/usr/share/doc/python3/python-policy.html/

/usr/share/doc/python3/python-policy.html

Name	Size	Mode	Actions
build_dependencies.html	3509	0644	edit dl rm
embed.html	3618	0644	edit dl rm
index.html	9720	0644	edit dl rm
module_packages.html	16866	0644	edit dl rm
other.html	2286	0644	edit dl rm
packaging_tools.html	7515	0644	edit dl rm
programs.html	7010	0644	edit dl rm
python.html	21522	0644	edit dl rm
python3.html	3630	0644	edit dl rm
upgrade.html	5160	0644	edit dl rm

Edit: /usr/share/doc/python3/python-policy.html/python3.html (3630B)

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Completing the move to Python 3</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="home" href="index.html" title="Debian Python Policy" /><link rel="up" href="index.html" title="Debian Python Policy" /><link rel="prev" href="index.html" title="Debian Python Policy" /><link rel="next" href="python.html" title="Chapter 2. Python Packaging" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. Completing the move to Python 3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="python.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="python3"></a>Chapter 1. Completing the move to Python 3</h1></div></div></div><p>
	  Debian has previously supported two Python stacks, one for Python 3
	  and one for Python 2.  The goal for Debian is to reduce this
	  to one stack, dropping the Python 2 stack and interpreter for
	  the Bullseye release.
	</p><p>
	  <a class="ulink" href="https://www.python.org/dev/peps/pep-0404/" target="_blank">PEP 404</a> states that no more major Python 2 releases
	  are planned, although the latest released minor version 2.7
	  will see some extended support, documented in
	  <a class="ulink" href="https://www.python.org/dev/peps/pep-0466/" target="_blank">PEP 466</a>.
	</p><p>
	  Packages in Debian should use Python 3. New packages must
	  use Python 3 from the initial upload, new upstream versions
	  for existing packages must use Python 3. If Python 2 is still
	  supported in Bullseye, selected packages may continue using
	  Python 2 until Python 3 support is available for those packages.
	  Please discuss all use of Python 2 on the debian-python
	  mailing list before uploading.
	</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
	      Applications should use Python 3 and must not be packaged
	      for Python 2 as well. If an application supports only
	      Python 2, the application may need to be removed from
	      Debian so that it does not block removal of other Python 2
	      packages.
	    </p></li><li class="listitem"><p>
	      Python libraries need to support Python 3 and new versions
	      must be packaged for Python 3. Existing Python 2 libraries
	      must not be dropped before the last reverse dependency is
	      removed. New Python 2 libraries must not be introduced.
	    </p></li><li class="listitem"><p>
	      Python 3 should be used for the packaging if the
	      packaging scripts use Python.
	    </p></li></ol></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="python.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Debian Python Policy </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Python Packaging</td></tr></table></div></body></html>

Chapter 1. Completing the move to Python 3

Chapter 1. Completing the move to Python 3
Prev		Next

Chapter 1. Completing the move to Python 3

Debian has previously supported two Python stacks, one for Python 3 and one for Python 2. The goal for Debian is to reduce this to one stack, dropping the Python 2 stack and interpreter for the Bullseye release.

PEP 404 states that no more major Python 2 releases are planned, although the latest released minor version 2.7 will see some extended support, documented in PEP 466.

Packages in Debian should use Python 3. New packages must use Python 3 from the initial upload, new upstream versions for existing packages must use Python 3. If Python 2 is still supported in Bullseye, selected packages may continue using Python 2 until Python 3 support is available for those packages. Please discuss all use of Python 2 on the debian-python mailing list before uploading.

Applications should use Python 3 and must not be packaged for Python 2 as well. If an application supports only Python 2, the application may need to be removed from Debian so that it does not block removal of other Python 2 packages.
Python libraries need to support Python 3 and new versions must be packaged for Python 3. Existing Python 2 libraries must not be dropped before the last reverse dependency is removed. New Python 2 libraries must not be introduced.
Python 3 should be used for the packaging if the packaging scripts use Python.

Prev		Next
Debian Python Policy	Home	Chapter 2. Python Packaging