Python은 고수준, 동적 개체 기반 프로그램이며, 네트워크 프로그램, 시스템 관리, 사운드와 그래팩을 위한 확장 클래스 라이브러리를 포함합니다. 데비안은 항상 적어도 두 버전 최근 파이썬 2, 그리고 최근 파이썬 3을 제공합니다. 추가 버전, 수많은 제3자 패키지도 제공할 수 있습니다. 파이썬은 데비안 생태계의 중요한 부분입니다.
파이썬은 배우기 쉽습니다. You can begin with the DebianWomen/PythonTutorial or the official online tutorial if you want to get started programming in Python. You might also be interested in the Python wiki, the Python FAQ, and the online documentation.
Software written in the Python programming language is executed by the Python interpreter. It is usually compiled into platform-independent bytecode files to increase performance. Python compiles and writes bytecode *.pyc files alongside the *.py sources. Extension modules can also be written in C, which are distributed as .so shared libraries.
Therefore, software written in pure Python can be distributed as source code or as compiled bytecode. The latter is similar to Java.
As such, with hundreds of Python modules and multiple versions of Python supported, Debian is the largest "integrated Python distribution". Users of other operating systems (e.g. Windows and OS X) can also benefit from this integrative effort by means of virtualization (e.g. see NeuroDebian VM page for easy way to start)
As of 2015-10-09 we now maintain all of our packages in Git. Here is team policy for using git for team packages.
Within the Debian project, Python packages are maintained by individual developers and three main teams:
pkg-python maintains the Python compiler/interpreter package.
Debian Python Modules Team maintains some Python modules and extensions.
Python Applications Packaging Team maintains some Python applications.
There are also :
지원되는 파이썬 버전
Debian 9 Stretch contains Python 2.7.13 and 3.5.3
Debian Jessie contains Python 2.7 (default), 3.4
Debian Wheezy contains Python 2.7 (default), 3.2
Debian Squeeze contains Python 2.5, 2.6 (the default), 3.1.
Debian Lenny contains Python 2.4 and 2.5 (the default).
Those links list the distribution(s) that ship the given versions of python:
Distribution(s) shipping python3.5
Distribution(s) shipping python3.4
Distribution(s) shipping python3.3
Distribution(s) shipping python3.2
Distribution(s) shipping python3.1
Distribution(s) shipping python3.0 (none)
Distribution(s) shipping python2.7
Distribution(s) shipping python2.6
Distribution(s) shipping python2.5 (none)
Distribution(s) shipping python2.4 (none)
Debian Python Policy for Python developers
The Debian Python Policy describes conventions for packaging and distributing Python code in Debian.
Feel free to ask any questions on firstname.lastname@example.org mailing list.
if you want to maintain a Python package, you have to know how the Debian Development works.
Deviations from upstream
Debian distributions modify upstream Python in a few ways that are important to understand. Of course, where at all possible, we try to minimize deviations from upstream, but here is an enumeration of the changes you might encounter on a Debian system (and derivatives, such as Ubuntu).
dist-packages instead of site-packages. Third party Python software installed from Debian packages goes into dist-packages, not site-packages. This is to reduce conflict between the system Python, and any from-source Python build you might install manually.
- The standard profile and pstats modules are not included, due to restrictive redistribution clauses in their license that don’t meet the DFSG. cProfile and hotshot are however included.
Also in Debian 7 (Wheezy), the python-virtualenv also uses distribute by default, but can enable classic setuptools with an optional switch. As above, in Debian 8 (Jessie) this just use the merged setuptools.
distutils setup scripts install files in /usr/local/ not sys.prefix (which is normally /usr/). This is because /usr/ is reserved for files installed from Debian packages. Note that /usr/local/lib/pythonX.Y/dist-packages is in sys.path so that modules not installed from Debian packages can still be accessed by the system Python. Tools like debhelper pass the --install-layout=deb option to the setup script while building a Debian package so that its installs files into /usr/ not /usr/local/.
Python 2.7, 3.3, and 3.4 are ?multiarch aware.
Style guide for packaging Python libraries (includes adding Python 3 support)
Style guide for packaging Python applications (includes Python 3 support)
There is a growing number of python-*-dbg packages for modules with extensions. They provide extensions built using python*-dbg libraries allowing to take advantage of GDB constantly improving support for debugging of Python modules and extensions. If you build extensions module, please provide corresponding -dbg package
Converting your package to dh_python2