./devel/py-setuptools, New Python packaging system

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 35.0.1, Package name: py27-setuptools-35.0.1, Maintainer: joerg

setuptools is a collection of enhancements to the Python distutils
that allow you to more easily build and distribute Python packages,
especially ones that have dependencies on other packages.

DEINSTALL [+/-]

Required to run:
[textproc/py-expat] [lang/python27] [lang/py-six] [devel/py-appdirs] [devel/py-packaging]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 7b91693a28b4e188f3ec4c99d9bd5386af110ad1
RMD160: 93beca54e8d629646fc9d56e0e73e99368ce48f2
Filesize: 609.632 KB

Version history: (Expand)


CVS history: (Expand)


   2017-04-23 01:43:20 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 35.0.1.

v35.0.1

    #992: Revert change introduced in v34.4.1, now considered invalid.
    #1016: Revert change introduced in v35.0.0 per #1014, referencing #436. The \ 
approach had unintended consequences, causing sdist installs to be missing \ 
files.
   2017-04-19 19:29:28 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 35.0.0.

v35.0.0
-------

* #436: In egg_info.manifest_maker, no longer read
  the file list from the manifest file, and instead
  re-build it on each build. In this way, files removed
  from the specification will not linger in the manifest.
  As a result, any files manually added to the manifest
  will be removed on subsequent egg_info invocations.
  No projects should be manually adding files to the
  manifest and should instead use MANIFEST.in or SCM
  file finders to force inclusion of files in the manifest.

v34.4.1
-------

* #1008: In MSVC support, use always the last version available for Windows SDK \ 
and UCRT SDK.

* #1008: In MSVC support, fix "vcruntime140.dll" returned path with \ 
Visual Studio 2017.

* #992: In msvc.msvc9_query_vcvarsall, ensure the
  returned dicts have str values and not Unicode for
  compatibilty with os.environ.

v34.4.0
-------

* #995: In MSVC support, add support for "Microsoft Visual Studio \ 
2017" and "Microsoft Visual Studio Build Tools 2017".

* #999 via #1007: Extend support for declarative package
  config in a setup.cfg file to include the options
  ``python_requires`` and ``py_modules``.
   2017-04-05 17:56:31 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 34.3.3.

v34.3.3
-------

* #967 (and #997): Explicitly import submodules of
  packaging to account for environments where the imports
  of those submodules is not implied by other behavior.
   2017-03-13 11:18:37 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 34.3.2.

v34.3.2
-------

* #993: Fix documentation upload by correcting
  rendering of content-type in _build_multipart
  on Python 3.
   2017-03-05 15:29:27 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 34.3.1.

v34.3.1
-------

* #988: Trap ``os.unlink`` same as ``os.remove`` in
  ``auto_chmod`` error handler.

* #983: Fixes to invalid escape sequence deprecations on
  Python 3.6.
   2017-02-27 11:42:34 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 34.3.0.

Fix test target.
4 tests failing, three due to pip not existing (we have pip3.6 et al.),
one because of ASCII locale.

v34.3.0
-------

* #941: In the upload command, if the username is blank,
  default to ``getpass.getuser()``.

* #971: Correct distutils findall monkeypatch to match
  appropriate versions (namely Python 3.4.6).
   2017-02-20 11:04:10 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Updated py-setuptools to 34.2.0.

v34.2.0
-------

* #966: Add support for reading dist-info metadata and
  thus locating Distributions from zip files.

* #968: Allow '+' and '!' in egg fragments
  so that it can take package names that contain
  PEP 440 conforming version specifiers.
   2017-02-08 13:11:22 by Thomas Klausner | Files touched by this commit (3) | Package updated
Log message:
Updated py-setuptools to 34.1.1.

v34.1.1
-------

* #953: More aggressively employ the compatibility issue
  originally added in #706.

v34.1.0
-------

* #930: ``build_info`` now accepts two new parameters
  to optimize and customize the building of C libraries.

v34.0.3
-------

* #947: Loosen restriction on the version of six required,
  restoring compatibility with environments relying on
  six 1.6.0 and later.

v34.0.2
-------

* #882: Ensure extras are honored when building the
  working set.
* #913: Fix issue in develop if package directory has
  a trailing slash.

v34.0.1
-------

* #935: Fix glob syntax in graft.

v34.0.0
-------

* #581: Instead of vendoring the growing list of
  dependencies that Setuptools requires to function,
  Setuptools now requires these dependencies just like
  any other project. Unlike other projects, however,
  Setuptools cannot rely on ``setup_requires`` to
  demand the dependencies it needs to install because
  its own machinery would be necessary to pull those
  dependencies if not present (a bootstrapping problem).
  As a result, Setuptools no longer supports self upgrade or
  installation in the general case. Instead, users are
  directed to use pip to install and upgrade using the
  ``wheel`` distributions of setuptools.

  Users are welcome to contrive other means to install
  or upgrade Setuptools using other means, such as
  pre-installing the Setuptools dependencies with pip
  or a bespoke bootstrap tool, but such usage is not
  recommended and is not supported.

  As discovered in #940, not all versions of pip will
  successfully install Setuptools from its pre-built
  wheel. If you encounter issues with "No module named
  six" or "No module named packaging", especially
  following a line "Running setup.py egg_info for package
  setuptools", then your pip is not new enough.

  There's an additional issue in pip where setuptools
  is upgraded concurrently with other source packages,
  described in pip #4253. The proposed workaround is to
  always upgrade Setuptools first prior to upgrading
  other packages that would upgrade Setuptools.