Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience.
...declaration of a directory as contributing to a package is a desirable property, rather than an obstacle. In particular, Jython developers noticed that Jython could easily mistake a directory that is a Java package as being a Python package, if there is no need to declare Python packages. Packages can stop filling out the namespace package's __init__.py. As a consequence, extend_path and declare_namespace become obsolete. Namespace packages can start providing non-trivial __init__.py implementa...
...package. Date: 18-Mar-2002 Documentation: Documented as "deprecated since release 2.3" since Python 2.2.2. Module name: mimetools Rationale: Supplanted by Python 2.2's email package. Date: 18-Mar-2002 Documentation: Documented as "deprecated since release 2.3" since Python 2.2.2. Module name: MimeWriter Rationale: Supplanted by Python 2.2's email package. Date: 18-Mar-2002 Documentation: Documented as "deprecated since releas...
...package. Classifiers are described in PEP 301. Examples: Classifier: Development Status :: 4 - Beta Classifier: Environment :: Console (Text Based) Requires (multiple use) Each entry contains a string describing some other module or package required by this package. The format of a requirement string is identical to that of a module or package name usable with the 'import' statement, optionally followed by a version declaration within parentheses. A version declaration is a series of condit...
...Package Index. "Releases" are uniquely identified snapshots of a project. "Distribution packages" are the packaged files which are used to publish and distribute a release. Depending on context, "package" may refer to either a distribution, or to an importable Python module that has a __path__ attribute and hence may also have importable submodules. "Source archive" and "VCS checkout" both refer to the raw source code for a release, prior to creation of an sdist or binary archive. An "sdist" is ...
...package support is somewhat simpler (no __ and __domain__) and differs in one crucial aspect: __init__.py is required, and loaded in the package's namespace instead of as a submodule. For more information, see Built-in Package Support. The new "re" module (Perl style regular expressions) is here. It is based on Philip Hazel's pcre code; the Python interfaces were put together by Andrew Kuchling. The regex module is declared obsolete. In support of the re module, a new form of string...
...packages that have contradictory build-requirements. E.g. if package1 build-requires pbr==1.8.1, and package2 build-requires pbr==1.7.2, then these cannot both be installed simultaneously into the global environment -- which is a problem when the user requests pip install package1 package2. Or if the user already has pbr==1.8.1 installed in their global environment, and a package build-requires pbr==1.7.2, then downgrading the user's version would be rather rude. It acts as a kind of public heal...
...Packages PEP:459 Title:Standard Metadata Extensions for Python Software Packages Author:Nick Coghlan <ncoghlan at gmail.com> BDFL-Delegate:Nick Coghlan <ncoghlan at gmail.com> Discussions-To:distutils-sig at python.org Status:Withdrawn Type:Standards Track Requires:426 Created:11-Nov-2013 Post-History:21-Dec-2013 Contents PEP Withdrawal Abstract Standard Extension Namespace The python.details extension License Keywords Classifiers Document names The python.proj...
...declaration. Indented lines below the function declaration declare parameters, one per line; lines below those that are indented even further are per-parameter docstrings. Finally, the first line dedented back to column 0 end parameter declarations and start the function docstring. Parameter docstrings are optional; function docstrings are not. Functions that specify no arguments may simply specify the function declaration followed by the docstring. Module and Class Declarations When a C fil...
...packages being the site dir and {version} as the previous, the license files would be installed to: site-packages/setuptools-{version}.dist-info/license_files/LICENSE site-packages/setuptools-{version}.dist-info/license_files/setuptools/_vendor/packaging/LICENSE site-packages/setuptools-{version}.dist-info/license_files/setuptools/_vendor/packaging/LICENSE.APACHE site-packages/setuptools-{version}.dist-info/license_files/setuptools/_vendor/packaging/LICENSE.BSD Conversion example Suppose we ...
...declaration within parentheses. The distutils project names should correspond to names as found on the Python Package Index. Version declarations must follow the rules described in Version Specifiers Examples: Requires-Dist: pkginfo Requires-Dist: PasteDeploy Requires-Dist: zope.interface (>3.5.0) Provides-Dist (multiple use) Each entry contains a string naming a Distutils project which is contained within this distribution. This field must include the project identified in the Name fiel...
...packages, each of which are independently developed and distributed. In order for her users to properly specify dependencies on the right versions of her packages, she specifies the version numbers in the namespace package's setup.py file. Because Carol wants to have to update one version number per package, she specifies the version number in her module and has the setup.py extract the module version number when she builds the sdist archive. David maintains a package in the standard library, ...
...package metadata 2.0) and related updates have been resolved. Terminology Reference is packaging terminology in Python documentation. Relationship with other PEPs PEP 8#package-and-module-names deals with code style guide, including names of Python packages and modules. It covers syntax of package/modules names. PEP 345 deals with packaging metadata, and defines name argument of the packaging.core.setup() function. PEP 420 deals with namespace packages. It brings support of namespace packag...
...Packages to Py3 Van Lindberg proposed the idea of possibly hiring one or two programmers in the next year to port packages to Python 3. There was a discussion rather this would be a good idea. The majority of the board +1 the idea. 9.2 Sam Berger Ewa Jodlowska was approached by Larry Berger (Sam's father) during PyConZA about furthering Sam's programming education. It has been decided that PyCon will sponsor his trip to the US to take part in the Young Coders tutorial and conf...
...packages. If Alice produces a class library protected by assertions, Bob cannot derive classes from Alice's library and expect proper checking of post-conditions and invariants. If they both use the same assertions package, then Bob can override Alice's methods yet still test against Alice's contract assertions. The natural place to find this assertions system is in the language's run-time library. Specification The docstring of any module or class can include invariant contracts marked off...
Version: None
Released: Feb. 23, 2014
Python 3.3.5 includes fixes for these important issues: a 3.3.4 regression in zipimport (see http://bugs.python.org/issue20621) a 3.3.4 regression executing scripts with a coding declared and Windows newlines (see http://bugs.python.org/issue20731) potential DOS using compression codecs in bytes.decode() (see http://bugs.python.org/issue19619 and http://bugs.python.org/issue20404) and also fixes quite a few other …
View Release Notes
Released: March 2, 2014
Released: March 9, 2014
...package support PEP 3151, reworking the OS and IO exception hierarchy PEP 3155, qualified name for classes and functions PEP 409, suppressing exception context PEP 414, explicit Unicode literals to help with porting PEP 418, extended platform-independent clocks in the "time" module PEP 412, a new key-sharing dictionary implementation that significantly saves memory for object-oriented code PEP 362, the function-signature object The new "faulthandler" module that helps diagnos...
...package" refers to packages as they are implemented in Python 3.2 and earlier. "portion" refers to a set of files in a single directory (possibly stored in a zip file) that contribute to a namespace package. "legacy portion" refers to a portion that uses __path__ manipulation in order to implement namespace packages. This PEP defines a new type of package, the "namespace package". Namespace packages today Python currently provides pkgutil.extend_path to denote a package as a namespace package...