packaging
Core utilities for Python packages
Core utilities for Python packages
To install this package, run one of the following:
Core utilities for Python packages
documentation_
If you run into bugs, you can file them in our issue tracker_.
You can also join #pypa on Freenode to ask questions or get involved.
.. _documentation: https://packaging.pypa.io/
.. _issue tracker: https://github.com/pypa/packaging/issues
Everyone interacting in the packaging project's codebases, issue trackers, chat
rooms, and mailing lists is expected to follow the PyPA Code of Conduct_.
.. _PyPA Code of Conduct: https://www.pypa.io/en/latest/code-of-conduct/
16.8 - 2016-10-29 ~~~~~~~~~~~~~~~~~
Fix markers that utilize in so that they render correctly.
Fix an erroneous test on Python RC releases.
16.7 - 2016-04-23 ~~~~~~~~~~~~~~~~~
python_implementation marker which was
an undocumented setuptools marker in addition to the newer markers.16.6 - 2016-03-29 ~~~~~~~~~~~~~~~~~
16.5 - 2016-02-26 ~~~~~~~~~~~~~~~~~
16.4 - 2016-02-22 ~~~~~~~~~~~~~~~~~
foo (==4).16.3 - 2016-02-21 ~~~~~~~~~~~~~~~~~
packaging.requirements:Requirement was overly strict when
matching legacy requirements.16.2 - 2016-02-09 ~~~~~~~~~~~~~~~~~
16.1 - 2016-02-07 ~~~~~~~~~~~~~~~~~
16.0 - 2016-01-19 ~~~~~~~~~~~~~~~~~
Relicense so that packaging is available under either the Apache License, Version 2.0 or a 2 Clause BSD license.
Support installation of packaging when only distutils is available.
Fix == comparison when there is a prefix and a local version in play.
(#41 <https://github.com/pypa/packaging/issues/41>__).
Implement environment markers from PEP 508.
15.3 - 2015-08-01 ~~~~~~~~~~~~~~~~~
#35 <https://github.com/pypa/packaging/issues/35>__15.2 - 2015-05-13 ~~~~~~~~~~~~~~~~~
Fix an error where the arbitary specifier (===) was not correctly
allowing pre-releases when it was being used.
Expose the specifier and version parts through properties on the
Specifier classes.
Allow iterating over the SpecifierSet to get access to all of the
Specifier instances.
Allow testing if a version is contained within a specifier via the in
operator.
15.1 - 2015-04-13 ~~~~~~~~~~~~~~~~~
SpecifierSet or not.15.0 - 2015-01-02 ~~~~~~~~~~~~~~~~~
Add Version().is_postrelease and LegacyVersion().is_postrelease to
make it easy to determine if a release is a post release.
Add Version().base_version and LegacyVersion().base_version to make
it easy to get the public version without any pre or post release markers.
Support the update to PEP 440 which removed the implied !=V.* when using
either >V or <V and which instead special cased the handling of
pre-releases, post-releases, and local versions when using >V or <V.
14.5 - 2014-12-17 ~~~~~~~~~~~~~~~~~
Normalize release candidates as rc instead of c.
Expose the VERSION_PATTERN constant, a regular expression matching
a valid version.
14.4 - 2014-12-15 ~~~~~~~~~~~~~~~~~
<) or greater than (>) operator.14.3 - 2014-11-19 ~~~~~~~~~~~~~~~~~
BACKWARDS INCOMPATIBLE Refactor specifier support so that it can sanely handle legacy specifiers as well as PEP 440 specifiers.
BACKWARDS INCOMPATIBLE Move the specifier support out of
packaging.version into packaging.specifiers.
14.2 - 2014-09-10 ~~~~~~~~~~~~~~~~~
Specifier.item in Specifier() and replace it with
Specifier().contains(item) in order to allow flags that signal if a
prerelease should be accepted or not.Specifier().filter() which will take an iterable and returns
an iterable with items that do not match the specifier filtered out.14.1 - 2014-09-08 ~~~~~~~~~~~~~~~~~
LegacyVersion and Version to be sorted together.packaging.version.parse() to enable easily parsing a version string
as either a Version or a LegacyVersion depending on it's PEP 440
validity.14.0 - 2014-09-05 ~~~~~~~~~~~~~~~~~
Summary
Core utilities for Python packages
Last Updated
Feb 8, 2017 at 03:28
License
BSD or Apache License, Version 2.0
Total Downloads
38