Mailman 3 June 2016 - Distutils-SIG

PyPi not allowing duplicate filenames
by Chris Barker 20 Apr '20

20 Apr '20

Hi all, PyPi does not allow duplicate file names -- this makes lots of sense, because you really don't want people to go to PyPi one day and grab a file, and then go there another day, grab a file with exactly the same name, and have it be a different file. However.... We are all too human, and make mistakes when doing a release. All to often someone pushed a broken file up to PyPi, often realizes it pretty quickly -- before anyone has a chance to even download it (or only the dev team as, for testing...). In fact, I was in a sprint last summer, and we decided to push our package up to PyPi -- granted, we were all careless amateurish noobs, but we ended up making I think 4! minor version bumps because we had done something stupid in the sdist. Also -- the latest numpy release got caught in this, too: """ * We ran into a problem with pipy not allowing reuse of filenames and a resulting proliferation of *.*.*.postN releases. Not only were the names getting out of hand, some packages were unable to work with the postN suffix. """ So -- I propose that PyPi allow projects to replace existing files if they REALLY REALLY want to. You should have to jump through all sorts of hoops, and make it really clear that it is a BAD IDEA in the general case, but it'd be good to have it be possible. After all -- PyPi does not take on responsibility for anything else about what's in those packages, and Python itself is all about "we're all consenting adults here" I suppose we could even put in some heuristics about how long the file as been there, how many times it's been downloaded, etc. Just a thought.....I really hate systems that don't let me roll back mistakes, even when I discover them almost immediately... -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker(a)noaa.gov

13 24

ImportError running 'test' on namespace package - other package in namespace not found
by Jason R. Coombs 17 Apr '20

17 Apr '20

I've got two projects: mynamespace.myprojectA and mynamespace.myprojectB myprojectB depends on myprojectA. I'm using setuptools 0.6c8 to manage both projects. Both projects are registered using 'setup develop'. Both projects are accessible from an interactive interpreter: PS C:\Users\me\projects> python Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import mynamespace.myprojectA >>> import mynamespace.myprojectB >>> from mynamespace.myprojectA import mymoduleZ However, when I run 'setup test' in myprojectB, the tests fail with File ".mymoduleZ.py", line NNN, in [some context] from mynamespace.myprojectA.mymoduleZ import MyClassC ImportError: No module named myprojectA.mymoduleZ In setup.py, the test_suite is nose.collector. I searched and couldn't find anyone else with this problem. Is this a supported configuration? Is there something I can do to make tests work with interdependent projects with the same root namespace? If there's not something obvious I should be doing differently, I'm happy to put together a minimal test case that reproduces the problem. Any suggestions are appreciated. Sincerely, Jason R. Coombs

3 6

Surviving a Compromise of PyPI - PEP 458 and 480
by Vladimir Diaz 12 Feb '20

12 Feb '20

Hello everyone, I am a research programmer at the NYU School of Engineering. My colleagues (Trishank Kuppusamy and Justin Cappos) and I are requesting community feedback on our proposal, "Surviving a Compromise of PyPI." The two-stage proposal can be reviewed online at: PEP 458 http://legacy.python.org/dev/peps/pep-0458/ PEP 480 http://legacy.python.org/dev/peps/pep-0480/ Summary of the Proposal: "Surviving a Compromise of PyPI" proposes how the Python Package Index (PyPI) can be amended to better protect end users from altered or malicious packages, and to minimize the extent of PyPI compromises against affected users. The proposed integration allows package managers such as pip to be more secure against various types of security attacks on PyPI and defend end users from attackers responding to package requests. Specifically, these PEPs describe how PyPI processes should be adapted to generate and incorporate repository metadata, which are signed text files that describe the packages and metadata available on PyPI. Package managers request (along with the packages) the metadata on PyPI to verify the authenticity of packages before they are installed. The changes to PyPI and tools will be minimal by leveraging a library, The Update Framework <https://github.com/theupdateframework/tuf>, that generates and transparently validates the relevant metadata. The first stage of the proposal (PEP 458 <http://legacy.python.org/dev/peps/pep-0458/>) uses a basic security model that supports verification of PyPI packages signed with cryptographic keys stored on PyPI, requires no action from developers and end users, and protects against malicious CDNs and public mirrors. To support continuous delivery of uploaded packages, PyPI administrators sign for uploaded packages with an online key stored on PyPI infrastructure. This level of security prevents packages from being accidentally or deliberately tampered with by a mirror or a CDN because the mirror or CDN will not have any of the keys required to sign for projects. The second stage of the proposal (PEP 480 <http://legacy.python.org/dev/peps/pep-0480/>) is an extension to the basic security model (discussed in PEP 458) that supports end-to-end verification of signed packages. End-to-end signing allows both PyPI and developers to sign for the packages that are downloaded by end users. If the PyPI infrastructure were to be compromised, attackers would be unable to serve malicious versions of these packages without access to the project's developer key. As in PEP 458, no additional action is required by end users. However, PyPI administrators will need to periodically (perhaps every few months) sign metadata with an offline key. PEP 480 also proposes an easy-to-use key management solution for developers, how to interface with a potential build farm on PyPI infrastructure, and discusses the security benefits of end-to-end signing. The second stage of the proposal simultaneously supports real-time project registration and developer signatures, and when configured to maximize security on PyPI, less than 1% of end users will be at risk even if an attacker controls PyPI and goes undetected for a month. We thank Nick Coghlan and Donald Stufft for their valuable contributions, and Giovanni Bajo and Anatoly Techtonik for their feedback. Thanks, PEP 458 & 480 authors.

7 53

Upgrading dependencies
by Charlie Moad 29 Apr '18

29 Apr '18

Is it currently possible to upgrade dependencies as well when upgrading a packages? If not, this would be a really nice feature to add to easy_install. Maybe a call like: easy_install --upgrade --upgrade-deps Package Obviously it makes sense to leave this off by default. Thanks, Charlie

2 1

Changes to --find-links and --upgrade in SVN
by Phillip J. Eby 29 Apr '18

29 Apr '18

Elvelind Grandin reported a problem with the "develop" command that turned out to be a flaw in its --find-links support. Specifically, it wasn't ever processing the links. :) In the process of fixing it, I wound up cleaning up an annoying (to me, at least) quirk of the previous workings of --find-links. It used to be that find-links would always be processed first, no matter what, even if you were doing a completely local operation. This would've been especially annoying if it carried over into "develop", so I made some changes. Now, if an item passed to --find-links is local (a filename or file: URL), or a direct link to an egg or other distribution, it is indexed immediately. Remote URLs are now only retrieved if a dependency can't be resolved locally, or if you use the -U or --upgrade options (this goes for "develop" too). Note that this is a behavior change for easy_install, which was effectively treating --find-links as though you'd specified --upgrade in certain cases. So, if you're used to getting upgrades downloaded as a result of using --find-links, please note that this will no longer happen. EasyInstall will now *only* go online if a dependency can't be resolved locally, if -U or --upgrade is used, or if you provided suitable direct URLs via an argument or --find-links, or via a link in a local .html file.

2 1

Problems with svn in windows
by Sharky On PTNet 29 Apr '18

29 Apr '18

Hi, I´m trying to do "easy_install setuptools==dev" in a windows box but have an error with svn command. """... 'svn' is not recognized as an internal or external command, ...""" I have installed TortoiseSVN but it seems that don't have command line, is all with the Explorer. Can you tell me what client I may use in windows? Thanks for all, Helio Pereira Sharky @ PTNet

3 2

local development scenarios
by tgreenwood 29 Apr '18

29 Apr '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm new to distutils/and the egg system. I have not researched the archives as much as I should, so please excuse me if this is familiar territory... Q: Is it possible for dependency checks to work for non pipy deployed eggs? - A.egg - B.egg (setup_requires and install_requires A.egg) - email A and B eggs to friend - tell friend to : easy_install B - but B.egg does not install A...in fact, in my test case, it fails b/c it cannot find A in pipy - in this example, what happens if friend does not have net connection on target machine? how can they install from the eggs alone and get the dep checking to work? Q: How does my friend run the unittests on the egg that they have just installed? As I am developing, I frequently run the unittests and after every bdist_egg build, I also run the unit tests that way, too. How can the consumer do the same? Q: One of my apps is a command line app, say foo.py is a command line app that takes arg1, arg2,... How can the user run this app when it is encased in an egg? Q: How do I define my own pipy? While I like the idea of deploying there for the overall community, I don't want to send my half baked code into the wild. But I'd like to try the general functionality of having a deploy site for my beta customers. How can I set this up? Thanks in advance. - -Todd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDl9Hfz6uXX4lQc/URAnY4AJ47DFHL/cpEltmqoUyGqzhsK5FjRACgt01v akc3Wh3IOXVv2jiS8TszhuE= =Rv/x -----END PGP SIGNATURE-----

5 12

Choice of dependencies?
by John J Lee 29 Apr '18

29 Apr '18

Is it possible for a package to depend on one of several packages, with the user having the option to pick? For example, my package P might depend on package A, plus either package B or package C. I know I could (ab)use extras_require, but in my case this is a real dependency rather than an optional extra. The other option I have is to just pick one of the dependencies (B or C in my example above), and thereby force people to install it even though it's not strictly required. Neither option seems particularly attractive. John

3 6

setuptools doc patch
by John J Lee 29 Apr '18

29 Apr '18

The comma removed by the patch below implies that users working from a Subversion checkout should not use EasyInstall to periodically fetch the latest version. That's not what you intended to say, I assume? http://peak.telecommunity.com/DevCenter/setuptools You should also inform your users of the need to run this command, if they -are working from a Subversion checkout, rather than using EasyInstall to +are working from a Subversion checkout rather than using EasyInstall to periodically fetch the latest version. Hmm, probably much better than the patch above: -You should also inform your users of the need to run this command, if they -are working from a Subversion checkout, rather than using EasyInstall to -periodically fetch the latest version. +If your users are working from a Subversion checkout rather than using +EasyInstall, you should also inform them of the need to run this command +to periodically fetch the latest version. John

2 2

Re: [Distutils] distutils install probs on suse 9.0
by Mats Wichmann 29 Apr '18

29 Apr '18

At 05:43 AM 5/18/2004, David Handy wrote: >On Tue, 18 May 2004, Floris van der Tak wrote: > >> my attempt to install the distutils on suse 9.0 (which provides python >> 2.3) fails: > >Why are you installing distutils on a system that already has Python 2.3 >installed? Python 2.3 normally comes with distutils as part of the Python >standard library. > >Did suse distribute a version of Python that had distutils removed? It should come from python-devel

2 1

Sample setup.py for Numeric Python
by Greg Ward 29 Apr '18

29 Apr '18

Hi again -- [cc'd to Paul Dubois: you said you weren't following the distutils sig anymore, but this directly concerns NumPy and I'd like to get your input!] here's that sample setup.py for NumPy. See below for discussion (and questions!). ------------------------------------------------------------------------ #!/usr/bin/env python # Setup script example for building the Numeric extension to Python. # This does sucessfully compile all the .dlls. Nothing happens # with the .py files currently. # Move this file to the Numerical directory of the LLNL numpy # distribution and run as: # python numpysetup.py --verbose build_ext # # created 1999/08 Perry Stoll __rcsid__ = "$Id: numpysetup.py,v 1.1 1999/09/12 20:42:48 gward Exp $" from distutils.core import setup setup (name = "numerical", version = "0.01", description = "Numerical Extension to Python", url = "http://www.python.org/sigs/matrix-sig/", ext_modules = [ ( '_numpy', { 'sources' : [ 'Src/_numpymodule.c', 'Src/arrayobject.c', 'Src/ufuncobject.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/numpy.def' } ), ( 'multiarray', { 'sources' : ['Src/multiarraymodule.c'], 'include_dirs' : ['./Include'], 'def_file': 'Src/multiarray.def' } ), ( 'umath', { 'sources': ['Src/umathmodule.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/umath.def' } ), ( 'fftpack', { 'sources': ['Src/fftpackmodule.c', 'Src/fftpack.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/fftpack.def' } ), ( 'lapack_lite', { 'sources' : [ 'Src/lapack_litemodule.c', 'Src/dlapack_lite.c', 'Src/zlapack_lite.c', 'Src/blas_lite.c', 'Src/f2c_lite.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/lapack_lite.def' } ), ( 'ranlib', { 'sources': ['Src/ranlibmodule.c', 'Src/ranlib.c', 'Src/com.c', 'Src/linpack.c', ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/ranlib.def' } ), ] ) ------------------------------------------------------------------------ First, what d'you think? Too clunky and verbose? Too much information for each extension? I kind of think so, but I'm not sure how to reduce it elegantly. Right now, the internal data structures needed to compile a module are pretty obviously exposed: is this a good thing? Or should there be some more compact form for setup.py that will be expanded later into the full glory we see above? I've already made one small step towards reducing the amount of cruft by factoring 'include_dirs' out and supplying it directly as a parameter to 'setup()'. (But that needs code not in the CVS archive yet, so I've left the sample setup.py the same for now.) The next thing I'd like to do is get that damn "def_file" out of there. To support it in MSVCCompiler, there's already an ugly hack that unnecessarily affects both the UnixCCompiler and CCompiler classes, and I want to get rid of that. (I refer to passing the 'build_info' dictionary into the compiler classes, if you're familiar with the code -- that dictionary is part of the Distutils extension-building system, and should not propagate into the more general compiler classes.) But I don't want to give these weird "def file" things standing on the order of source files, object files, libraries, etc., because they seem to me to be a bizarre artifact of one particular compiler, rather than something present in a wide range of C/C++ compilers. Based on the NumPy model, it seems like there's a not-too-kludgy way to handle this problem. Namely: if building extension "foo": if file "foo.def" found in same directory as "foo.c" add "/def:foo.def" to MSVC command line this will of course require some platform-specific code in the build_ext command class, but I figured that was coming eventually, so why put it off? ;-) To make this hack work with NumPy, one change would be necessary: rename Src/numpy.def to Src/_numpy.def to match Src/_numpy.c, which implements the _numpy module. Would this be too much to ask of NumPy? (Paul?) What about other module distributions that support MSVC++ and thus ship with "def" files? Could they be made to accomodate this scheme? Thanks for your feedback -- Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

4 5

Can now compile simple extensions
by Greg Ward 29 Apr '18

29 Apr '18

Hi all -- at long last, I found the time to hack in the ability to compile extension modules to the Distutils. Mainly, this meant adding a 'build_ext' command which uses a CCompiler instance for all its dirty work. I also had to add a few methods to CCompiler (and, of course, UnixCCompiler) to make this work. And I added a new module, 'spawn', which takes care of running sub-programs more efficiently and robustly (no shell involved) than os.system. That's needed, obviously, so we can run the compiler! If you're in the mood for grubbing over raw source code, then get the latest from CVS or download a current snapshot. See http://www.python.org/sigs/distutils-sig/implementation.html for a link to the code snapshot. I'm still waiting for more subclasses of CCompiler to appear. At the very least, we're going to need MSVCCompiler to build extensions on Windows. Any takers? Also, someone who knows the Mac, and how to run compilers programmatically there, will have to figure out how to write a Mac-specific concrete CCompiler subclass. The spawn module also needs a bit of work to be portable. I suspect that _win32_spawn() (the intended analog to my _posix_spawn()) will be easy to implement, if it even needs to go in a separate function at all. It looks from the Python Library documentation for 1.5.2 that the os.spawnv() function is all we need, but it's a bit hard to figure out just what's needed. Windows wizards, please take a look at the 'spawn()' function and see if you can make it work on Windows. As for actually compiling extensions: well, if you can figure out the build_ext command, go ahead and give it a whirl. It's a bit cryptic right now, since there's no documentation and no example setup.py. (I have a working example at home, but it's not available online.) If you feel up to it, though, see if you can read the code and figure out what's going on. I'm just hoping *I'll* be able to figure out what's going on when I get back from the O'Reilly conference next week... ;-) Enjoy -- Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Two fixes (at last)
by Greg Ward 29 Apr '18

29 Apr '18

Hi all -- at long last, I have fixed two problems that a couple people noticed a while ago: * I folded in Amos Latteier's NT patches almost verbatim -- just changed an `os.path.sep == "/"' to `os.name == "posix"' and added some comments bitching about the inadequacy of the current library installation model (I think this is Python's fault, but for now Distutils is slavishly aping the situation in Python 1.5.x) * I fixed the problem whereby running "setup.py install" without doing anything else caused a crash (because 'build' hadn't yet been run). Now, the 'install' command automatically runs 'build' before doing anything; to make this bearable, I added a 'have_run' dictionary to the Distribution class to keep track of which commands have been run. So now not only are command classes singletons, but their 'run' method can only be invoked once -- both restrictions enforced by Distribution. The code is checked into CVS, or you can download a snapshot at http://www.python.org/sigs/distutils-sig/distutils-19990607.tar.gz Hope someone (Amos?) can try the new version under NT. Any takers for Mac OS? BTW, all parties involved in the Great "Where Do We Install Stuff?" Debate should take a good, hard look at the 'set_final_options()' method of the Install class in distutils/install.py; this is where all the policy decisions about where to install files are made. Currently it apes the Python 1.5 situation as closely as I could figure it out. Obviously, this is subject to change -- I just don't know to *what* it will change! Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Package versioning
by Timothy Docker 29 Apr '18

29 Apr '18

Hi all, I've been aware that the distutils sig has been simmerring away, but until recently it has not been directly relevant to what I do. I like the look of the proposed api, but have one question. Will this support an installed system that has multiple versions of the same package installed simultaneously? If not, then this would seem to be a significant limitation, especially when dependencies between packages are considered. Assuming it does, then how will this be achieved? I am presently managing this with a messy arrangement of symlinks. A package is installed with its version number in it's name, and a separate directory is created for an application with links from the unversioned package name to the versioned one. Then I just set the pythonpath to this directory. A sample of what the directory looks like is shown below. I'm sure there is a better solution that this, and I'm not sure that this would work under windows anyway (does windows have symlinks?). So, has this SIG considered such versioning issues yet? Cheers, Tim -------------------------------------------------------------- Tim Docker timd(a)macquarie.com.au Quantative Applications Division Macquarie Bank -------------------------------------------------------------- qad16:qad $ ls -l lib/python/ total 110 drwxr-xr-x 2 mts mts 512 Nov 11 11:23 1.1 -r--r----- 1 root mts 45172 Sep 1 1998 cdrmodule_0_7_1.so drwxr-xr-x 2 mts mts 512 Sep 1 1998 chart_1_1 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Fnorb_0_7_1 dr-xr-x--- 3 mts mts 512 Nov 11 11:21 Fnorb_0_8 drwxr-xr-x 3 mts mts 1536 Mar 3 12:45 mts_1_1 dr-xr-x--- 7 mts mts 512 Nov 11 11:22 OpenGL_1_5_1 dr-xr-x--- 2 mts mts 1024 Nov 11 11:23 PIL_0_3 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Pmw_0_7 dr-xr-x--- 2 mts mts 512 Nov 11 11:21 v3d_1_1 qad16:qad $ ls -l lib/python/1.1 total 30 lrwxrwxrwx 1 root other 29 Apr 10 10:43 _glumodule.so -> ../OpenGL_1_5_1/_glumodule.so lrwxrwxrwx 1 root other 30 Apr 10 10:43 _glutmodule.so -> ../OpenGL_1_5_1/_glutmodule.so lrwxrwxrwx 1 root other 22 Apr 10 10:43 _imaging.so -> ../PIL_0_3/_imaging.so lrwxrwxrwx 1 root other 36 Apr 10 10:43 _opengl_nummodule.so -> ../OpenGL_1_5_1/_opengl_nummodule.so lrwxrwxrwx 1 root other 27 Apr 10 10:43 _tkinter.so -> ../OpenGL_1_5_1/_tkinter.so lrwxrwxrwx 1 mts mts 21 Apr 10 10:43 cdrmodule.so -> ../cdrmodule_0_7_1.so lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 chart -> ../chart_1_1 lrwxrwxrwx 1 root other 12 Apr 10 10:43 Fnorb -> ../Fnorb_0_8 lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 mts -> ../mts_1_1 lrwxrwxrwx 1 root other 15 Apr 10 10:43 OpenGL -> ../OpenGL_1_5_1 lrwxrwxrwx 1 root other 33 Apr 10 10:43 opengltrmodule.so -> ../OpenGL_1_5_1/opengltrmodule.so lrwxrwxrwx 1 root other 33 Apr 10 10:43 openglutil_num.so -> ../OpenGL_1_5_1/openglutil_num.so lrwxrwxrwx 1 root other 10 Apr 10 10:43 PIL -> ../PIL_0_3 lrwxrwxrwx 1 mts mts 10 Apr 10 10:43 Pmw -> ../Pmw_0_7 lrwxrwxrwx 1 root other 10 Apr 10 10:43 v3d -> ../v3d_1_1

3 2

[Distutils-sig] distutils charter and interscript
by John Skaller 29 Apr '18

29 Apr '18

3 2

Versioned trove classifiers for Django
by James Bennett 06 Apr '17

06 Apr '17

Following up on some IRC discussion with other folks: There is precedent (Plone) for PyPI trove classifiers corresponding to particular versions of a framework. So I'd like to get feedback on the idea of expanding that, particularly in the case of Django. The rationale here is that the ecosystem of Django-related packages is quite large, but -- as I know all too well from a project I'm working on literally at this moment -- it can be difficult to ensure that all of one's dependencies are compatible with the version of Django one happens to be using. Adding trove classifier support at the level of individual versions of Django would, I think, greatly simplify this: tools could easily analyze which packages are compatible with an end user's chosen version, there'd be far less manual guesswork, etc., and the rate of creation of new classifiers would be relatively low (we tend to have one X.Y release/year or thereabouts, and that's the level of granularity needed). Assuming there's consensus around the idea of doing this, what would be the correct procedure for getting such classifiers set up and maintained?

5 17

namespace_package
by KP 12 Sep '16

12 Sep '16

I'm not sure where the issue is, but when I specify a namespace_package in the setup.py file, I can indeed have multiple packages with the same base (foo.bar, foo.blah, etc...). The files all install in to the same directory. It drops the foo/__init__.py that would be doing the extend_path, and instead adds a ".pth" file that is a bit over my head. The problem is that it does not seem to traverse the entire sys.path to find multiple foo packages. If I do not specify namespace_packages and instead just use the pkgutil.extend_path, then this seems to allow the packages to be in multiple places in the sys.path. Is there something additional for the namespace_package that i need to specify in order for all of the sys.path to be checked? I'm using 18.5 setuptools....but I am not sure if this somehow ties in to wheel/pip, since I'm using that for the actual install.

4 19

Missing IPv6 support on pypi.python.org
by Baptiste Jonglez 13 Jul '16

13 Jul '16

Hi, pypi.python.org is currently not reachable over IPv6. I know this issue was brought up before [1,2]. This is a real issue for us, because our backend servers are IPv6-only (clients never need to talk to backend servers, they go through IPv4-enabled HTTP frontends). So, deploying packages from pypi on the IPv6-only servers is currently a pain. What is the roadmap to add IPv6 support? It seems that Fastly has already deployed IPv6 [3]. Thanks, Baptiste [1] https://mail.python.org/pipermail/distutils-sig/2014-June/024465.html [2] https://bitbucket.org/pypa/pypi/issues/90/missing-ipv6-connectivity [3] http://bgp.he.net/AS54113#_prefixes6

4 6

Request for comment: Proposal to change behaviour of pip install
by Pradyun Gedam 29 Jun '16

29 Jun '16

Hello List! There is currently a proposal to change the behaviour to pip install to upgrade a package that is passed even if it is already installed. This behaviour change is accompanied with a change in the upgrade strategy - pip would stop “eagerly” upgrading dependencies and would become more conservative, upgrading a dependency only when it doesn’t meet lower constraints of the newer version of a parent. Moreover, the behaviour of pip install --target would also be changed so that --upgrade no longer affects it. A PEP-style write-up ( https://gist.github.com/pradyunsg/4c9db6a212239fee69b429c96cdc3d73) documents the reasoning behind this proposed change, what the change is and some alternate proposals that were rejected in the discussions. This is a request for comments on the pull-request implementing this proposal (https://github.com/pypa/pip/pull/3806) for your views, thoughts and possible concerns related to it. — Cheers, Pradyun Gedam

14 37

pip behavior
by Steve Spicklemire 28 Jun '16

28 Jun '16

Hi Distutils-SIG Folks, If this is not the best place for a ‘pip’ question, please direct me to a better destination. I have several virtual environments. As far as I know they should all be about the same WRT the python binary that was used to create them (home-brew python2.7.11/OSX). However they have different behavior WRT pip install. I’m trying to track down the cues that pip uses to choose a binary wheel, or a source/build install. I’ve been using ‘pip -v’ to get some hints, but it’s still not clear. I’ve saved two log files that illustrate the issue: https://dl.dropboxusercontent.com/u/20562746/pydev_pip_log.txt https://dl.dropboxusercontent.com/u/20562746/pytest_pip_log.txt So my question is: How can I determine why pip is choosing ‘wheel’ in some cases and ‘source’ in others when I have the same python build in both cases? thanks! -steve

2 2

enscons, a prototype SCons-powered wheel & sdist builder
by Daniel Holth 26 Jun '16

26 Jun '16

I've been working on a prototype Python packaging system powered by SCons called enscons. https://bitbucket.org/dholth/enscons . It is designed to be an easier way to experiment with packaging compared to hacking on distutils or setuptools which are notoriously difficult to extend. Now it is at the very earliest state where it might be interesting to others who are less familiar with the details of pip and Python package formats. Enscons is able to create wheels and source distributions that can be installed by pip. Source distributions built with enscons use pyproject.toml from PEP 518 ( https://www.python.org/dev/peps/pep-0518/ ) to install enscons before setup.py is run, and since pip does not yet implement PEP 518, include a setup.py shim for PEP 518. The same pyproject.toml includes most of the arguments normally passed to setuptools.setup(), which are used to create the metadata files needed by pip. Enscons converts pip's setup.py arguments to SCons ones and then invokes SCons, and the project's SConstruct does the rest. For a normal from-pypi installation, enscons generates just enough egg_info to let pip build a wheel, then pip builds and installs the wheel which has more complete metadata. Of course SCons is more interesting for more complicated projects. I've been working on building my pysdl2-cffi binding with SCons. It includes a custom Python code generation step that distutils knew nothing about. It's practically a one-liner to add my custom build step to SCons, and it knows how to rebuild each part of the project only when its dependencies have changed. I don't know how to do that with setuptools. It is still a very early prototype. Don't expect it to be very good. Here are some of its limitations: - There is no error checking. - The sdists can only be built inside virtualenvs; otherwise pip complains that --user and --target cannot be used together. - It also doesn't work if one of the pyproject.toml build requirements conflicts with something that's already installed. - 'pip install .' doesn't work; it still tries to invoke 'setup.py install', which is not implemented. - 'setup.py develop' is not implemented. Try PYTHONPATH. - I am not an experienced SCons user. It also relies on what I'm sure will be a short-lived repackaging of SCons called 'import_scons' that makes 'python -m SCons' work, and includes a Python 3 version of SCons from github.com/timj/scons that seems to work well enough for my purposes. On the plus side, it's short. If you're interested in implementing Python packaging in SCons, or are interested in the straightforward but tedious task of copying just enough distutils trickery to implement a robust Python C extension compiler in SCons, then perhaps you should check out enscons. Here is a SConstruct for enscons itself: import pytoml as tomlimport ensconsmetadata = dict(toml.load(open('pyproject.toml')))['tool']['enscons'] env = Environment(tools=['default', 'packaging', enscons.generate], PACKAGE_METADATA=metadata, WHEEL_TAG='py2.py3-none-any', ROOT_IS_PURELIB=True)py_source = Glob('enscons/*.py') sdist = env.Package( NAME=env['PACKAGE_NAME'], VERSION=env['PACKAGE_METADATA']['version'], PACKAGETYPE='src_zip', target=['dist/' + env['PACKAGE_NAME'] + '-' + env['PACKAGE_VERSION']], source=FindSourceFiles() + ['PKG-INFO', 'setup.py'], ) env.NoClean(sdist) env.Alias('sdist', sdist)env.Whl('purelib', py_source, root='.') Thanks!

2 2

Re: [Distutils] Benchmark regression feeds
by Pauli Virtanen 24 Jun '16

24 Jun '16

Sorry for the unrelated noise --- sent to the wrong mailing list :/

1 0

Benchmark regression feeds
by Pauli Virtanen 24 Jun '16

24 Jun '16

Hi, In case someone is interested in getting notifications of performance regressions in the Numpy and Scipy benchmarks, this is available as Atom feeds at: https://pv.github.io/numpy-bench/regressions.xml https://pv.github.io/scipy-bench/regressions.xml

1 0

Notice: PyPI APIs now return 403 when accessed via HTTP
by Donald Stufft 24 Jun '16

24 Jun '16

In part of an ongoing effort to improve the security of PyPI, instead of redirecting (or silently allowing) requests made over HTTP to PyPI APIs, these APIs will now return a 403 and require people to make the initial request over HTTPS. This does not affect the UI portions of the site that are designed to be used by humans, for these we will still redirect (which will cause the browser to see the HSTS header and force the user to use HTTPS from then on out). Thanks! — Donald Stufft

2 1

Proposal: using /etc/os-release in the "platform tag" definition for wheel files
by Vitaly Kruglikov 23 Jun '16

23 Jun '16

On 22 June 2016 at 08:51, Nathaniel Smith <njs at pobox.com> wrote: > I believe the status is that there's general consensus that something like > this would be useful, but there's no one who is currently actively working > in it. Thanks everyone for following up on my questions. This helps a lot. In particular, thank you for pointing me to manylinux1. https://www.python.org/dev/peps/pep-0513 appears to be incredibly well written, with excellent insights. I will likely adopt the manylinux1 approach. <https://www.python.org/dev/peps/pep-0513/>

1 0

Re: [Distutils] Proposal: using /etc/os-release in the "platform tag" definition for wheel files
by Nathaniel Smith 23 Jun '16

23 Jun '16

I believe the status is that there's general consensus that something like this would be useful, but there's no one who is currently actively working in it. On Jun 22, 2016 5:53 AM, "Vitaly Kruglikov" <vkruglikov(a)numenta.com> wrote: There have been no updates in over a year. Has this effort died, or transitioned to another medium? Thx _______________________________________________ Distutils-SIG maillist - Distutils-SIG(a)python.org https://mail.python.org/mailman/listinfo/distutils-sig

3 2

Proposal: using /etc/os-release in the "platform tag" definition for wheel files
by Vitaly Kruglikov 23 Jun '16

23 Jun '16

Thanks everyone for following up on my questions. This helps a lot. In particular, thank you for pointing me to manylinux1. https://www.python.org/dev/peps/pep-0513 appears to be incredibly well written, with excellent insights. I will likely adopt the manylinux1 approach. <https://www.python.org/dev/peps/pep-0513/>

1 0

Re: [Distutils] Proposal: using /etc/os-release in the "platform tag" definition for wheel files
by Nathaniel Smith 22 Jun '16

22 Jun '16

There are still use cases for distro-specific wheels, though -- some examples include Raspbian wheels (manylinux1 is x86/x86-64 only), Alpine Linux wheels (manylinux1 is glibc only), internal deploys that want to build on Ubuntu 14.04 and deploy on 14.04 and don't need the hassle of generating manylinux-style binaries but would like a more meaningful platform tag than "linux", and for everyone who wants to extend wheel metadata to allow dependencies on external distro packages then having distro-specific wheels is probably a necessary first step. -n On Jun 22, 2016 09:49, "Noah Kantrowitz" <noah(a)coderanger.net> wrote: Manylinux has mostly replaced it as that covers the platforms 99% of people worry about. The tooling for manylinux is more complex than this would have been, but sunk cost etc etc and now that we have it might as well save everyone some headache. --Noah > On Jun 22, 2016, at 8:51 AM, Nathaniel Smith <njs(a)pobox.com> wrote: > > I believe the status is that there's general consensus that something like this would be useful, but there's no one who is currently actively working in it. > > On Jun 22, 2016 5:53 AM, "Vitaly Kruglikov" <vkruglikov(a)numenta.com> wrote: > There have been no updates in over a year. Has this effort died, or transitioned to another medium? Thx > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG(a)python.org > https://mail.python.org/mailman/listinfo/distutils-sig > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG(a)python.org > https://mail.python.org/mailman/listinfo/distutils-sig _______________________________________________ Distutils-SIG maillist - Distutils-SIG(a)python.org https://mail.python.org/mailman/listinfo/distutils-sig

5 6

Proposal: using /etc/os-release in the "platform tag" definition for wheel files
by Vitaly Kruglikov 22 Jun '16

22 Jun '16

There have been no updates in over a year. Has this effort died, or transitioned to another medium? Thx

1 0

Removal of wheels deleting more than the data files
by Sylvain Corlay 20 Jun '16

20 Jun '16

I discovered a quite serious bug in wheels ( http://bugs.python.org/issue27317) When specifying an empty list for the list of data_files in a given directory, the entire directory is being deleted on uninstall of the wheel, even if it contained other resources from other pacakges. Example: from setuptools import setup > setup(name='remover', data_files=[('share/plugins', [])]) The expected behavior is that only the specified list of files is removed, (which is empty in that case). When the list is not empty, the behavior is the one expected. For example, from setuptools import setup > setup(name='remover', data_files=[('share/plugins', ['foobar.json'])]) will only remove `foobar.json` on uninstall and the `plugins` directory will not be removed if it is not empty. Thanks, Sylvain

2 2

Docker, development, buildout, virtualenv, local/global install
by Reinout van Rees 17 Jun '16

17 Jun '16

Hi, Buzzword bingo in the subject... Situation: I'm experimenting with docker, mostly in combination with buildout. But it also applies to pip/virtualenv. I build a docker container with a Dockerfile: install some .deb packages, add the current directory as /code/, run buildout (or pip), ready. Works fine. Now local development: it is normal to mount the current directory as /code/, so that now is overlayed over the originally-added-to-the-docker /code/. This means that anything done inside /code/ is effectively discarded in development. So a "bin/buildout" run has to be done again, because the bin/, parts/, eggs/ etc directories are gone. Same problem with a virtualenv. *Not* though when you run pip directly and let it install packages globally! Those are installed outside of /code in /usr/local/somewhere. A comment and a question: - Comment: "everybody" uses virtualenv, but be aware that it is apparently normal *not* to use virtualenv when building dockers. - Question: buildout, like virtualenv+pip, installs everything in the current directory. Would an option to install it globally instead make sense? I don't know if it is possible. Reinout -- Reinout van Rees http://reinout.vanrees.org/ reinout(a)vanrees.org http://www.nelen-schuurmans.nl/ "Learning history by destroying artifacts is a time-honored atrocity"

7 19

Fw: Re: [Webmaster] Upload the package to the Pypi problem
by taochengwei＠emar.com 16 Jun '16

16 Jun '16

From: Tim Golden Date: 2016-06-16 15:26 To: taochengwei(a)emar.com; webmaster Subject: Re: [Webmaster] Upload the package to the Pypi problem Please repost this to the distutils-sig mailing list: https://mail.python.org/mailman/listinfo/distutils-sig TJG On 16/06/2016 07:23, taochengwei(a)emar.com wrote: > I run `python setup.py register sdist bdist_egg upload`, > """ > running upload > Submitting dist/SpliceURL-0.1.tar.gz to http://pypi.python.org/pypi > Upload failed (403): Must access using HTTPS instead of HTTP > Submitting dist/SpliceURL-0.1-py2.7.egg to http://pypi.python.org/pypi > Upload failed (403): Must access using HTTPS instead of HTTP > """ > My system: > python 2.6.6 > setuptools (23.0.0) > > My .pypirc > """ > [distutils] > index-servers = > pypi > > [pypi] > repository=https://pypi.python.org/pypi > username=saintic > password=zzz > """ > I change a Centos7 system, is the same(no pypirc, python2.7). > > > ------------------------------------------------------------------------ > _______________________________________________ > Webmaster mailing list > Webmaster(a)python.org > https://mail.python.org/mailman/listinfo/webmaster >

2 1

If you want wheel to be successful, provide a build server.
by Thomas Güttler 14 Jun '16

14 Jun '16

If you want wheel to be successful, **provide a build server**. Quoting the author of psutil: https://github.com/giampaolo/psutil/issues/824#issuecomment-221359292 {{{ On Linux / Unix the only way you have to install psutil right now is via source / tarball. I don't want to provide wheels for Linux (or other UNIX platforms). I would have to cover all supported python versions (7) both 32 and 64 bits, meaning 14 extra packages to compile and upload on PYPI on every release. I do that for Windows because installing VS is an order of magnitude more difficult than installing gcc on Linux/UNIX but again: not willing to do extra work on that front (sorry). What you could do is create a wheel yourself with python setup.py build bdist_wheel by using the same python/arch version you have on the server, upload it on the server and install it with pip. }}} What do you think? Regards, Thomas Güttler -- Thomas Guettler http://www.thomas-guettler.de/

17 45

Uploading to Warehouse
by Donald Stufft 13 Jun '16

13 Jun '16

Hey all, As anyone here who has uploaded anything to PyPI recently is aware of, PyPI's uploading routine has been in a semi broken state for awhile now. It will regularly raise a 500 error (but will often still record the release, but sometimes only a partial release). Well, the good news is, that Warehouse's upload routines should generally be good enough to use now. This will be more or less the same as if you uploaded to PyPI itself (they share a backing data store) but hitting the newer, better code base instead of the slowly decaying legacy code base. You can upload via Warehouse by editing your ~/.pypirc file and making it look something like this: [distutils] index-servers = pypi warehouse [pypi] username:<username> password:<password> [warehouse] repository:https://upload.pypi.io/legacy/ username:<username> password:<password> Alternatively, you can ditch the [warehouse] section, and just totally switch over to this by doing: [distutils] index-servers = pypi [pypi] repository:https://upload.pypi.io/legacy/ username:<username> password:<password> Then you can upload using ``twine upload -r warehouse dist/*`` or ``twine upload dist/*`` based upon which of the above options you picked. This code is not as battle tested as PyPI itself is, so if you run into any bugs please file an issue with https://github.com/pypa/warehouse. This code should generally give a successful response all of the time (given the upload itself was good) and properly utilizes database transactions so that it should completely eliminate the cases where you get a partial upload. Hopefully this will help solve some of the problems folks are having with PyPI in the interim before we can completely switch over to Warehouse. — Donald Stufft

3 2

How to register my python package which relys on the output of other project on pypi
by Young Yang 12 Jun '16

12 Jun '16

Hi, I'm writing a python-binding project for project A written in C++. Project A is on github. It supports compiling itself to produce .so in linux or .dll in windows. My python-binding project contains depends on the .dll and .so file. Now I want to register my package on pypi. So that users can install my package with only running `pip install XXXX`. I have to support both windows and linux. The only solution I can figure out is to include both .dll and .so in my package. This will end up with both .so and .dll installed in any platforms. It sounds dirty. Is there any better ways to achieve my goal? PS: The compile process of Project A is a little complicated, so I can't use python Extension to build my dynamic library. This question comes after this question https://mail.python.org/pipermail/distutils-sig/2016-June/029059.html Thanks in advance :) -- Best wishes, Young Yang

2 2

Switch PyPA from IRC to Gitter or similar
by Jason R. Coombs 11 Jun '16

11 Jun '16

In #pypa-dev, I raised the possibility of moving our PyPA support channels from IRC to another hosted solution that enables persistence. Although IRC has served us well, there are systems now with clear feature advantages, which are crucial to my continuous participation: - always-on experience; even if one’s device is suspended or otherwise offline. - mobile support — the in-cloud experience is essential for low power and intermittently connected devices. - push notifications allow a project leader to remain largely inactive in a channel, but attention raised promptly when users make a relevant mention. - continuous, integrated logging for catching up on the conversation. Both Gitter and Slack offer the experience I’m after, with Gitter feeling like a better fit for open-source projects (or groups of them). I’ve tried using IRCCloud, and it provides a similar, suitable experience on the same IRC infrastructure, with one big difference. While Gitter and Slack offer the above features for free, IRCCloud requires a $5/user/month subscription (otherwise, connections are dropped after two hours). I did reach out to them to see if they could offer some professional consideration for contributors, but I haven’t heard from them. Furthermore, IRCCloud requires an additional account on top of the account required for Freenode. In addition to the critical features above, Gitter and Slack offer other advantages: - For Gitter, single-sign on using the same Github account for authentication and authorization means no extra accounts. Slack requires one new account. - An elegant web-based interface as a first-class feature, a lower barrier of entry for users. - Zero-install or config. - Integration with source code and other systems. It’s because of the limitations of these systems that I find myself rarely in IRC, only joining when I have a specific issue, even though I’d like to be permanently present. Donald has offered to run an IRC bouncer for me, but such a bouncer is only a half-solution, not providing the push notifications, mobile apps (IRC apps exist, but just get disconnected, and often fail to connect on mobile provider networks), or integrated logging. I note that both Gitter and Slack offer IRC interfaces, so those users who prefer their IRC workflow can continue to use that if they so choose. I know there are other alternatives, like self-hosted solutions, but I’d like to avoid adding the burden of administering such a system. If someone wanted to take on that role, I’d be open to that alternative. I’d like to propose we move #pypa-dev to /pypa/dev and #pypa to /pypa/support in gitter. Personally, the downsides to moving to Gitter (other than enacting the move itself) seem negligible. What do you think? What downsides am I missing?

11 13

Re: [Distutils] Distutils improvements regarding header installation and building C extension modules
by Tim Smith 08 Jun '16

08 Jun '16

On Wed, May 25, 2016 at 1:24 PM Sylvain Corlay <sylvain.corlay(a)gmail.com> wrote: > *2) On the need for something like pip.locations.distutils_scheme in > distutils* > (http://bugs.python.org/issue26955) > > When installing a python package that has a directive for the install_headers > distutils command, these headers are usually installed under the main > python include directory, which can be retrieved with > sysconfig.get_path('include') or directly referred to as the 'include' string > when setting the include directories of an extension module. > > However, on some systems like OS X, headers for extension modules are not > located in under the python include directory > > /usr/local/Cellar/pythonX/X.Y.Z/Frameworks/Python.framework/Versions/X.Y/include/pythonX.Y > > but in > > /usr/local/include/pythonX.Y. > > Is there a generic way to find the location where headers are installed in > a python install? pip.locations has a distutils_scheme function which seems > to be returning the right thing, but it seems to be a bit overkill to > require pip. On the other side, no path returned by sysconfig corresponds > to `/usr/local/include/pythonX.Y`. As a Homebrew maintainer this sounds like something that Homebrew could influence. Are there any packages in the wild that use this mechanism? It seems that headers are mostly installed beneath site-packages. I don't have strong feelings about whether Homebrew should have better support for install_headers or whether that would be straightforward to implement but IIRC we've had no prior reports of this causing trouble. Thanks, Tim

2 2

Deprecating PyPI as an OpenID Provider
by Donald Stufft 07 Jun '16

07 Jun '16

Just a heads up, I do not intend to implement the “Use PyPI as an OpenID Provider” functionality in Warehouse. Looking at the actual usage of this, it appears that very few people have ever taken advantage of it (a total of 201 (user, site) combinations in the database of what people have set to “Allow Always”) and I don’t believe it’s worth continuing. Longer term, Python should get a centralized Sign on across all it’s web properties, which could re-implement this feature for folks who want it. If you’re using this for anything, I recommend migrating off of it onto something else. Warehouse Issue: https://github.com/pypa/warehouse/issues/60 — Donald Stufft

4 3

on integrated docs in Warehouse and PyPI
by Jason R. Coombs 05 Jun '16

05 Jun '16

I had some thoughts on documentation integration (and its deprecation in Warehouse), which I wrote up here: https://paper.dropbox.com/doc/Integrated-Docs-is-an-Essential-Feature-HEqnF… I include the full text below for ease of access and response. Yesterday, as I was migrating Setuptools from PyPI to Warehouse due to this issue<https://github.com/pypa/setuptools/issues/589>, Donald alerted me to the fact that Warehouse does not plan to support documentation hosting<https://github.com/pypa/setuptools/issues/604#issuecomment-223614048>, and as a result, integrated documentation for the packaging infrastructure is deprecated. At first blush, this decision seems like a sound one - decouple independent operations and allow a mature, established organization like RTD<https://readthedocs.org/> to support and manage Python Package documentation. I have nothing but respect for RTD; I reference them here only as the prime example of a third-party doc hosting solution. After spending most of a day working on getting just one project documentation (mostly) moved from PyPI to RTD, I’ve realized there are several shortcomings with this approach. Integrated hosting provides several benefits not offered by RTD: * Uniform custody - the person or team that owns/maintains the package also owns/maintains the documentation with a single point of management and authorization. * Shared credentials - the accounts used to administer the packages are re-used to authenticate authorized users to the documentation. RTD requires a separate set of accounts for each user involved with the documentation. * Shared naming - a name registered as a package is automatically reserved for the documentation. * Automatic linkage - PyPI provides a Package Documentation link on each package that has documentation. * Control over the build process - although RTD does provide excellent hooks for customization and control, the process is essentially out of the hands of the operator. Thus when issues like this<https://github.com/rtfd/readthedocs.org/issues/2254> arise (probably rarely), the user is at the mercy of the system. With PyPI hosting, it was possible to manually build and upload docs when necessary and to control every aspect of the build process, including platform, Python version, etc. * One obvious choice - although RTD today is the obvious choice for hosting, I can see other prominent alternatives - using Github pages or self hosting or perhaps another service will emerge that’s more integrated with the packaging process. Having a sanctioned, integrated documentation hosting gives users confidence that it’s at least a good default choice if not the best one. * API access - Although RTD hopes to provide support for project creation through an API, it currently only allows querying through the public API. Therefore, it’s not feasible through tools to mechanically configure projects in RTD. Each project has to be manually configured and administered. For me, this last limitation is the most onerous. I maintain dozens of projects, many of them in collaboration with other teams, and in many of those, I rely on a model implementation<https://github.com/jaraco/skeleton> that leverages PyPI hosting as part of the package release process to publish documentation. Moving each of these projects to another hosting service would require the manual creation and configuration of another project for each. As I consider the effort it would take to port all of these projects and maintain them in a new infrastructure, I’m inclined to drop documentation support for all but the most prominent projects. The linkage provided by PyPI was a most welcome feature, and I’m really sad to see it go. I’d be willing to give up item 5 (Control) if the other items could be addressed.

9 11

Re: [Distutils] Alternate long_description formats, server-side
by Nick Coghlan 05 Jun '16

05 Jun '16

On 3 Jun 2016 4:03 am, "Donald Stufft" <donald(a)stufft.io> wrote: > > >> On Jun 2, 2016, at 9:16 PM, Nick Timkovich <prometheus235(a)gmail.com> wrote: >> >> I can definitely believe there are more important things to do, but some of us aren't versed in the intricacies of what's up top and don't have the familiarity to dive in. Us GitHub plebs are just raring to work on a feature we think is within our grasp ;-) >> > > Yup! Nick was speaking to why folks like myself haven’t done it yet- If some enterprising person (perhaps you!) takes the time to write up a PEP and work it through the process, then there’s no reason to wait for me (or Nick, or any of the other core team) to do it :) Right, the key part of my post is the second paragraph: we actually now have a relatively simple mechanism to capture proposals like this one, which is issues and pull requests against the "specifications" section of the Python packaging user guide on GitHub. Previously a key sticking point was not having a way to document added fields without a full PEP, which imposed way too much overhead for adding a simple attribute like Provides-Extra or the Description-Format field being considered here. For this to work, I think the concrete changes you would need would be: - Python packaging user guide to document the new field in the core metadata spec - setuptools to support setting it - Warehouse to respect it for all defined rendering formats - potentially legacy PyPI to support respecting it at least for reStructured text and Markdown (treating others as plain text) - PyPUG again to provide usage docs once the default tools support it Cheers, Nick. > > > — > Donald Stufft > > >

1 0

How to build python-packages depends on the output of other project
by Young Yang 04 Jun '16

04 Jun '16

hi, I'm writing python-binding for project A. My python-binding depends on the compile output of project A(It is a .so file), and the project A is not installed in the system(so we can't find the .so files in the system libraries pathes) What's the elegant way to package my python-binding, so that I can install everything by run `python setup.py` ? Any suggestions and comments will be appreciated :) -- Best wishes, Young

4 5

Accessing tests_require and setup_requires from the setup.py
by Christopher Baines 03 Jun '16

03 Jun '16

I'm trying to write a script to get information about a source distributions requirements (from the source distribution), but I'm not sure how to access the tests_require and setup_requires that can sometimes be found in the setup.py? Apologies if this is really simple, and I've just missed the answer, but I've searched for it a few times now, and not come up with anything. Thanks, Chris

6 8

Alternate long_description formats, server-side
by Nick Timkovich 03 Jun '16

03 Jun '16

When I brought up enabling Markdown previously, I was a bit over-eager and started talking implementation before there was any sort of consensus about it in principle, so it was a bit of a straw-man. The previous discussion seemed to rest with the onus being on the user to do it themselves, perhaps by installing (the non-Python) pandoc (non-trivial on Windows) as well as pypandoc and then integrating it into twine or some such. There seems to be a chasm between the GitHubbers that have various issues and PRs to this effect on the pypa/readme_renderer repo that are met with a frustrating silence from people with commit-power. Is the solution to basically write a full spec (PEP?) before touching any code? That seems like an actionable solution, but is it simply going to be rejected out-of-hand because of the "just learn rST" sentiment among the maintainers?

3 4

Officially deferring the Metadata 2.0 specification
by Nick Coghlan 02 Jun '16

02 Jun '16

Metadata 2.0 has been deferred-in-practice for quite some time, but I just updated the PEP itself to reflect the deferral and link to more of the incremental improvement PEPs: https://hg.python.org/peps/rev/94c1afae202e This makes the current policy that enhancement proposals should avoid depending on the definition and implementation of metadata 2.0 explicit. Regards, Nick. P.S. PEP 459 (standard metadata extensions) depends on 426, and has also been marked as Deferred -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

1 0

PyPi upload fails with TypeError
by Luís de Sousa 02 Jun '16

02 Jun '16

Dear all, I am trying to upload a new package to PyPi with this command: $ python3 setup.py sdist upload The process seems to go on well until the running upload bit, at which point I get this exception: Traceback (most recent call last): File "setup.py", line 33, in <module> "Topic :: Scientific/Engineering :: GIS", File "/usr/lib/python3.4/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.4/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/usr/lib/python3.4/distutils/dist.py", line 974, in run_command cmd_obj.run() File "/usr/lib/python3.4/distutils/command/upload.py", line 65, in run self.upload_file(command, pyversion, filename) File "/usr/lib/python3.4/distutils/command/upload.py", line 139, in upload_file user_pass = (self.username + ":" + self.password).encode('ascii') TypeError: Can't convert 'NoneType' object to str implicitly I verified that Topic :: Scientific/Engineering :: GIS is a valid topic. What else am I missing? Thank you, Luís Sent from [ProtonMail](https://protonmail.ch), encrypted email based in Switzerland.

5 13