Mailman 3 July 2014 - Distutils-SIG

Installing setuptools on an un-networked computer
by Peter Ganong July 22, 2014

July 22, 2014

Hi, I am doing research with confidential data on a Windows 7 computer not connected to the Internet. I can bring files in on a thumb drive. How can I install setuptools? To be clear, the issue is not the one answered in the help file here <https://pythonhosted.org/setuptools/easy_install.html#installing-on-un-netw…>, but is how to install setuptools itself on an unnetworked drive. Thanks, Peter -- Peter Ganong PhD Candidate in Economics at Harvard scholar.harvard.edu/ganong/

3 2

503 backend read error on PyPI
by Wichert Akkerman July 18, 2014

July 18, 2014

Just seen on https://pypi.python.org/pypi from a Dutch IP: Error 503 backend read error backend read error Guru Mediation: Details: cache-iad2132-IAD 1405663962 2954825964 Wichert.

1 2

setuptools develop command garbles binary files specified as scripts setup() parameter on windows
by David Genest July 17, 2014

July 17, 2014

Hi, In our environment, we are using the scripts parameter to package external binary files, which is really a practical use case: 1) it allows for bundling of executables in our package python distribution (with pertaining dlls etc) 2) the binary is available in an activated virtualenv For the install case, everything is ok, the binaries are correctly installed. But for the develop command, setuptools garbles the binary by copying the binary file opened in text mode and writing it in binary mode. This is because of the line ending translation. I implemented a naive fix, only to be surprised by the python3 unicode management, and caused a regression. (see https://bitbucket.org/pypa/setuptools/issue/210/on-windows-binary-files-spe…) The less naive approach to the problem was implemented in https://bitbucket.org/pypa/setuptools/pull-request/60/fix-regression-in-iss… but the pull request was rejected. But the problem still stands. How can I use the develop command and not have my binaries specified as scripts be garbled. Jason R. Coombs argued that this change would add undocumented special casing, but I am inclined to disagree because the use case works: * on *nix platforms (because the open function does not translate line endings (the "b" mode has no effect on this platform)) * it already works when we go through the install flow (on every platform) * there is a discrepancy between install and develop semantics, for the scripts parameter I would like to know what is the take in the community on this. Note that this is the first time I contribute a change, so I may not be up to speed with all the dos and don'ts. Thanks. David.

3 5

PyPI not rendering ReST long_description
by Wichert Akkerman July 16, 2014

July 16, 2014

I just uploaded a new pyramid_sqlalchemy package to PyPI. Looking at the distribution page at https://pypi.python.org/pypi/pyramid_sqlalchemy PyPI is not rendering ReST. I can’t figure out why though: according to both “python setup.py check” and "python setup.py --long-description | rst2html-2.7.py > /dev/null” there are no ReST syntax errors in me description. Is there any way to see why PyPI is not rendering my ReST? Wichert.

4 10

devpi-2.0.0: web/search UI, replication, fixes
by holger krekel July 16, 2014

July 16, 2014

devpi-2.0.0: web, search, replication for PyPI indexes ========================================================== The devpi system in version 2.0 brings tons of fixes and new features for the private github-style pypi caching server, most notably: - a new web interface featuring search of metadata and documentation as well as easier navigation and showing of test results per release file. - a new transactional storage system (based on sqlite) supporting real-time replication over http. - a new (experimental) hook system for extending server-side functionality. - ported to a solid web framework and wsgi-server: pyramid and waitress. Upgrade note: devpi-server-2.0 requires to ``--export`` your 1.2 server state and then using ``--import`` with the new version before you can serve your private packages through devpi-server-2.0.0. Also, please checkout the web plugin if you want to have a web interface:: http://doc.devpi.net/2.0/web.html Here is a Quickstart tutorial for efficient pypi-mirroring on your laptop:: http://doc.devpi.net/2.0/quickstart-pypimirror.html And if you want to manage your releases or implement staging as an individual or within an organisation:: http://doc.devpi.net/2.0/quickstart-releaseprocess.html If you want to host a devpi-server installation with nginx/supervisor and access it from clients from different hosts:: http://doc.devpi.net/2.0/quickstart-server.html More documentation here:: http://doc.devpi.net/2.0/ many many thanks to Florian Schulze who implemented the new ``devpi-web`` package and helped with many other improvements. have fun, Holger Krekel, merlinux GmbH 2.0.0 -------------- devpi-server: - major revamp of the internal core of devpi to support replication (both master and server code), a plugin architecture with the new devpi-web plugin providing a new web interface. Mostly done by Florian Schulze and Holger Krekel. - moved all html views except for files and the simple index to new devpi-web package. Thanks to Florian Schulze for the PR. - implement issue103: By default if you register a package in an index, no lookup on pypi is made for that package anymore. You have to add the package to the pypi_whitelist of the index to let pypi releases be mixed in. This is to prevent malicious uploads on pypi to overwrite private packages. - change json api to get rid of the different meaning of URLs with and without a trailing slash. "/{user}/" is now the same as "/user" and always lists indices. "/{user}/{index}" and "/{user}/{index}/ now always lists the index config and the contained per-stage projects (not inherited ones). - switch the wsgi app to use Pyramid and waitress for WSGI serving. - don't refresh releaselinks from the mirroring thread but rather rely on the next access to do it. - fix issue98: deleting a project config or a project version now accepts names which map to the canonical name of a project. - fix issue82 and fix issue81: root/pypi now provides the same attributes as normal indexes and results in a 409 MethodNotAllowed http code when trying to change the config. - fix issue91: make serverport available as well. Thanks David Bonner. - fix issue100: support large file uploads. As we switched away from bottle to pyramid, the body-size limit is gone. - fix issue99: make "devpi-server --start" etc work when devpi-server is not itself on PATH (by using sys.argv[0] for finding the binary) - fix issue84: uploading of wheels where the registered package name has an underscore works despite a wheel's metadata carrying hyphens instead. At submit-file time we now lookup the registered name and use that instead of assuming the one coming with the wheel is the correct one. - add refresh button on root/pypi project simple index pages which clears the internal cache to force a refetch from PyPI. - implement issue75: We use the custom X-Devpi-Auth header for authentication now, instead of overwriting the Authentication header. - added experimental support for using client certificates when running as a replica of a server running behind a proxy devpi-client: - Compatibility with devpi-server >= 2.0.0 - introduce "patchjson PATH JSONFILE" command which allows to send a request containing a json data structure to a specified path - fix issue85: "devpi list -v" now shows package names with latest versions. - implement issue75: We use the custom X-Devpi-Auth header for authentication now, instead of overwriting the Authentication header. - added experimental support for basic authentication by parsing user and password from the url given to the "devpi use" command. - issue74: added experimental support for client side certificates via "devpi use --client-cert" devpi-web: - initial release

1 1

PyPI changelog support, releases.json / common NEWS.rst format?
by mario＠include-once.org July 15, 2014

July 15, 2014

I'm currently tinkering on a freshmeat substitute. And for automating release announcements been looking around for common package meta data schemes. PyPIs /pypi/pkgname/json (or the xmlrpc interface) looks quite interesting. It obviously mostly targets dependency management and systemic categorization. So from googling around this never came up: But would it be feasible to include a version changelog / release summary via du.register? Of course, I'm referring to a human-readable "This version adds and fixes..." changelog, not the (name, version, timestamp) journal tuple. The releases{} per-URL `comment_text` seems widely unused. Was that its purpose? I hope this isn't getting too off-topic, this is -just for comparison and context- what I'm intending to eventually map PyPI release streams onto: http://fossil.include-once.org/freshcode/wiki/releases.json There are probably other priorities for distutils / warehouse currently. So alternatively, is there a semi-standard for NEWS.txt or CHANGELOG etc. files within Python packages? Cheeseshop project homepages which also include a release notes list via `long_description` seem far and few between. I actually found just one: https://pypi.python.org/pypi/py-translate Which seems to share a reStructuredText source for documentation and pypi homepage: https://raw.githubusercontent.com/jjangsangy/py-translate/master/HISTORY.rst (I'd have presumed Markdown-style release notes to be favoured.) Anyway, is there an estimate on how many packages include release notes at all?

3 2

PyPI XMLRPC interface no longer works with Python 2.6
by M.-A. Lemburg July 8, 2014

July 8, 2014

I just tried the documented interfaces for PyPI (https://wiki.python.org/moin/PyPIXmlRpc) with Python 2.6 and it fails with an error: > python pypirpc.py Traceback (most recent call last): File "pypirpc.py", line 7, in <module> pprint.pprint(client.package_releases('egenix-web-installer-test')) File "/usr/local/python-2.6-ucs2/lib/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args) File "/usr/local/python-2.6-ucs2/lib/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose File "/usr/local/python-2.6-ucs2/lib/python2.6/xmlrpclib.py", line 1253, in request return self._parse_response(h.getfile(), sock) File "/usr/local/python-2.6-ucs2/lib/python2.6/xmlrpclib.py", line 1390, in _parse_response p.close() File "/usr/local/python-2.6-ucs2/lib/python2.6/xmlrpclib.py", line 604, in close self._parser.Parse("", 1) # end of data xml.parsers.expat.ExpatError: no element found: line 1, column 0 The call works with Python 2.7. It appears that xmlrpclib is not receiving any body data from the server. The returned data in 2.7 looks completely harmless: send: "POST /pypi HTTP/1.1\r\nHost: pypi.python.org\r\nAccept-Encoding: gzip\r\nUser-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com)\r\nContent-Type: text/xml\r\nContent-Length: 185\r\n\r\n<?xml version='1.0'?>\n<methodCall>\n<methodName>package_releases</methodName>\n<params>\n<param>\n<value><string>egenix-web-installer-test</string></value>\n</param>\n</params>\n</methodCall>\n" reply: 'HTTP/1.1 200 OK\r\n' header: Server: nginx/1.6.0 header: Content-Type: text/xml header: charset: UTF-8 header: Strict-Transport-Security: max-age=31536000; includeSubDomains header: Transfer-Encoding: chunked header: Accept-Ranges: bytes header: Date: Tue, 08 Jul 2014 14:19:41 GMT header: Via: 1.1 varnish header: Connection: keep-alive header: X-Served-By: cache-fra1229-FRA header: X-Cache: MISS header: X-Cache-Hits: 0 header: X-Timer: S1404829181.210045,VS0,VE325 body: "<?xml version='1.0'?>\n<methodResponse>\n<params>\n<param>\n<value><array><data>\n<value><string>0.2.0</string></value>\n</data></array></value>\n</param>\n</params>\n</methodResponse>\n" Could this be a network error rather than a program one ? The code in 2.7 does a retry in case of a connection reset or abort, which code in 2.6 and earlier does not apply. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jul 08 2014) >>> Python Projects, Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2014-07-21: EuroPython 2014, Berlin, Germany ... 13 days to go ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/

2 7

pip, virtualenv, setuptools on Windows
by M.-A. Lemburg July 7, 2014

July 7, 2014

I wonder what our story is for the pip, virtualenv, setuptools packaging setup on Windows. At the moment, the only way to get this setup seems to be following guides such as these: http://www.tylerbutler.com/2012/05/how-to-install-python-pip-and-virtualenv… But that's not really how Windows users expect things to work. They want to click on an installer, preferably a MSI one, since that integrates well with managed corporate Windows environments, and then expect everything to just work. Much in the same way they install Python itself. Is there anything planned in this area ? Hint: If someone were to send in a grant request to build such an installer for Windows, I'm sure the PSF board would love to fund work such work. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jul 07 2014) >>> Python Projects, Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2014-07-21: EuroPython 2014, Berlin, Germany ... 14 days to go ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/

6 8

wheel 0.24.0 released
by Daniel Holth July 6, 2014

July 6, 2014

The much-anticipated 0.24.0 release of wheel has occurred. - The python tag used for pure-python packages is now .pyN (major version only). This change actually occurred in 0.23.0 when the --python-tag option was added, but was not explicitly mentioned in the changelog then. - wininst2wheel and egg2wheel removed. Use "wheel convert [archive]" instead. - Wheel now supports setuptools style conditional requirements via the extras_require={} syntax. Separate 'extra' names from conditions using the : character. Wheel's own setup.py does this. (The empty-string extra is the same as install_requires.) These conditional requirements should work the same whether the package is installed by wheel or by setup.py. So we support and convert setuptools' conditional requiremenst to METADATA. However, although pkg_resources.working_set.by_key['wheel']._dep_map is correct, pip install wheel[extraname] doesn't seem to work at all; this bug may be fixed in an unreleased pip? Daniel Holth

1 0

Specifying Python version as part of requirements
by Brett Cannon July 6, 2014

July 6, 2014

I just checked PEP 440 and pip doesn't seem to have anything specific, so I thought I would ask if there is any way now or in the future to specify that a dependency is only needed for certain versions of Python? My current use case is I want to use unittest2, but pip errors out during installation under Python 3 of it since unittest2 imports itself and triggers a syntax error. Instead of having to hack around this by making it a conditional include in my setup.py I would like to declare that I only need it in Python 2.x in a requirements.txt file or something.

3 7