conda-forge / setuptools-feedstock

A conda-smithy repository for setuptools.

About setuptools-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/pypa/setuptools

Package license: MIT

Summary: Download, build, install, upgrade, and uninstall Python packages

Development: https://github.com/pypa/setuptools

Documentation: http://pythonhosted.org/setuptools/

Setuptools is a fully-featured, actively-maintained, and stable library designed to facilitate packaging Python projects.

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing setuptools

Installing setuptools from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, setuptools can be installed with conda:

conda install setuptools

or with mamba:

mamba install setuptools

It is possible to list all of the versions of setuptools available on your platform with conda:

conda search setuptools --channel conda-forge

or with mamba:

mamba search setuptools --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search setuptools --channel conda-forge

# List packages depending on `setuptools`:
mamba repoquery whoneeds setuptools --channel conda-forge

# List dependencies of `setuptools`:
mamba repoquery depends setuptools --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating setuptools-feedstock

If you would like to improve the setuptools recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/setuptools-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @isuruf
• @jakirkham
• @msarahan
• @nicoddemus
• @ocefpaf
• @rgommers
• @xhochy

setuptools-feedstock's Issues

@conda-forge-admin, please update circle

@conda-forge-admin, please update circle

py39 win64 build broken

Currently failing with

https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/220132/logs/107

2020-10-09T11:46:40.8740773Z (%PREFIX%) %SRC_DIR%>%PREFIX%\python.exe bootstrap.py 
2020-10-09T11:46:40.9339477Z adding minimal entry_points
2020-10-09T11:46:40.9350318Z Regenerating egg_info
2020-10-09T11:46:41.4551459Z running egg_info
2020-10-09T11:46:41.4560766Z writing setuptools.egg-info\PKG-INFO
2020-10-09T11:46:41.4565158Z writing dependency_links to setuptools.egg-info\dependency_links.txt
2020-10-09T11:46:41.4576973Z writing entry points to setuptools.egg-info\entry_points.txt
2020-10-09T11:46:41.4579893Z writing requirements to setuptools.egg-info\requires.txt
2020-10-09T11:46:41.4583172Z writing manifest file 'setuptools.egg-info\SOURCES.txt'
2020-10-09T11:46:41.4746734Z reading manifest file 'setuptools.egg-info\SOURCES.txt'
2020-10-09T11:46:41.4753850Z reading manifest template 'MANIFEST.in'
2020-10-09T11:46:41.5540239Z warning: no files found matching '*.py' under directory 'tests'
2020-10-09T11:46:41.6268732Z writing manifest file 'setuptools.egg-info\SOURCES.txt'
2020-10-09T11:46:43.8871650Z Traceback (most recent call last):
2020-10-09T11:46:43.8872791Z   File "D:\bld\setuptools_1602243830115\work\bootstrap.py", line 59, in <module>
2020-10-09T11:46:43.8874752Z     __name__ == '__main__' and ensure_egg_info()
2020-10-09T11:46:43.8875604Z   File "D:\bld\setuptools_1602243830115\work\bootstrap.py", line 40, in ensure_egg_info
2020-10-09T11:46:43.8877864Z     run_egg_info()
2020-10-09T11:46:43.8878597Z   File "D:\bld\setuptools_1602243830115\work\bootstrap.py", line 56, in run_egg_info
2020-10-09T11:46:43.8880018Z     subprocess.check_call(cmd)
2020-10-09T11:46:43.8880529Z   File "D:\bld\setuptools_1602243830115\_h_env\lib\subprocess.py", line 373, in check_call
2020-10-09T11:46:43.8883375Z     raise CalledProcessError(retcode, cmd)
2020-10-09T11:46:43.8884154Z subprocess.CalledProcessError: Command '['D:\\bld\\setuptools_1602243830115\\_h_env\\python.exe', 'setup.py', 'egg_info']' returned non-zero exit status 3221225477.

update to version 33.1.0

Python 3 packages missing __pycache__ have .pyc

Appears that the Python 3 packages built here do not have __pycache__ directories as they would during a normal Python install. Instead they appear to have .pyc files as if they were Python 2 installs. Have confirmed this is not an issue with setuptools itself and that this is unique to the conda-build process.

xref: conda-forge/conda-smithy#289

We may need to pull the releases of setuptools 58.5.x

pypa/setuptools#2849

@conda-forge-admin, please add user @xhochy

Additional comment:

No response

Remove Python versioned `easy_install`?

We have a copy of easy_install that is versioned based on the Python version (e.g. easy_install-2.7). There has been some discussion in some cases about removing such things. If that is agreeable, we should do it here too. Have raised upstream issue ( pypa/setuptools#726 ) to see if we can get a build option to make this just work for us. There are ways to do this manually. Though doing it manually is a bit cumbersome. Maybe we should see if there is actually agreement over these types of removals first and then proceed. Opened issue ( conda-forge/conda-forge.github.io#205 ) for discussion on whether such removals should be pursued or not.

Linux uploads appear to be done by pelson?

This must simply be a matter of what token is used, but it appears all the Linux uploads for setuptools have been done by @pelson. Now I don't think this is actually the case as I have seen this right after the CI uploaded them. This doesn't appear to be the case with all feedstocks. pip for instance does not have this issue. Would be nice if we could correct this issue so as not to give the wrong impression about how these binaries were uploaded.

@conda-forge-admin, add noarch: python

Issue:

Environment (conda list):

$ conda list

Details about conda and system ( conda info ):

$ conda info

@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Loading conda-specific _sysconfigdata is broken with >=50.0.0

ref: conda-forge/admin-requests#120

setuptools <58 for py310

It looks like keepalive still uses use_2to3, which was finally removed in the 58.x line of setuptools. Pinning to <58 gets an unsatsifiable error.

conda-forge/keepalive-feedstock#13 (comment)

The usptream keepalive, which hasn't been updated in a few years, is a dependency of sparqlwrapper (WIP feedstock PR) and therefore rdflib, so we need to figure out something, or that whole ecosystem will stay blocked... though I'm doing some investigation there (will report back).

I don't know how wide-spread use_2to3 is, but as there's at least one other, I guess we could start a branch with ABI backports? The simplest play for keepalive would be 57.x, but maybe before the big change which corresponds to the window of missing releases?

@conda-forge-admin, please re-render

@conda-forge-admin, please re-render.

@conda-forge-admin add user @rgommers

• I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about conda and system ( conda info ):

$ conda info

conda-forge setuptools has files in conflict with conda-forge python

Just stumbled onto this in conda's master-branch integration testing

conda.exceptions.ClobberError: Conda no longer clobbers existing files without the use of the --force option.
  source path:      /usr/local/Cellar/python3/3.5.2_1/Frameworks/Python.framework/Versions/3.5/pkgs/setuptools-29.0.1-py35_0/lib/python3.5/__pycache__/__future__.cpython-35.pyc
  destination path: /var/folders/cp/7r2s_s593j7_cpdtxxsmct880000gp/T/21388fe5/lib/python3.5/__pycache__/__future__.cpython-35.pyc

Happens from an empty env when installing conda-forge python then conda-forge setuptools.

I've looked at the actual contents of both

• https://conda.anaconda.org/conda-forge/osx-64/python-3.5.2-2.tar.bz2
• https://conda.anaconda.org/conda-forge/osx-64/setuptools-29.0.1-py35_0.tar.bz2

As the exception indicates, the first clobbered file is lib/python3.5/__pycache__/__future__.cpython-35.pyc.

Conda 4.3 will have a pre-check phase before it starts mutating environments on disk--so that we don't fail half-way through an operation that should otherwise be transactional. However, as is, 4.3 will not be able to install conda-forge python with conda-forge setuptools.

Setuptools 48 may be broken on Linux

As suggested by the build failures on conda-forge/pillow-feedstock#80 . Bog-standard Linux/x86_64 builds are failing with:

2020-07-03T17:08:55.0395186Z   cc -pthread -shared -Wl,-O2 ... -o build/lib.linux-x86_64-3.6/PIL/_imaging.pypy36-pp73-x86_64-linux-gnu.so
2020-07-03T17:08:55.0417062Z   error: [Errno 2] No such file or directory: 'cc': 'cc'

In that PR the Linux/ppc64le builds still pulled in setuptools 47 and succeeded. MacOS builds succeeded, Windows builds failed for a different reason.

Setuptools 69.1.0 requires Python >= 3.8

There seems to be a mismatch regarding the Python version in conda-forge:

setuptools-feedstock/recipe/meta.yaml

Line 22 in 1977454

- python >=3.7

and the Python version declared by Setuptools 69.1.0:

Requires-Python: >=3.8

Produce Python 3.7 packages

setuptools version 34.0.1

setuptools version 34.0.1 has been released and is available on PyPI. There was a change to the bootstrap.py script which introduced a dependency on pip. This causes a circular dependency which is causing issues, see #55.

Reported the issue to upstream in pypa/setuptools#950

Missing python2 version constraint

conda create -c conda-forge -n test_setuptools_py27 python=2.7 installs setuptools>=45 which is incompatible with python2