Packaging no.6
From mtlpython
Contents |
[edit]
Presentation
Sprint on the Python packaging tools and libraries.
The sprint will take place at Brasseurs Numériques' office at 1124 Marie-Anne on 2010-07-15 starting at 18h30 EDT (UTC-2) and going as long as there are people standing.
Bring your laptop or make a pairing agreement on the mailing list before hand. Attendance is limited to 12 sprinters so please RSVP below.
[edit]
Who will attend
- Yannick Gingras
- George Peristerakis
- Nicolas Cadou
- Alex Gal
- Luis Rojas
- Alexis Métaireau (remote from France)
- Éric Araujo (remote from France)
[edit]
How to prepare
- read the Hitchhiker’s Guide to Packaging
- create a bitbucket account
- ask on the mailing list for the commit right on the Montréal-Python repo
- pick a task before hand and discuss it on the distutils2 mailing list
[edit]
Possible tasks
Here's a list of possible tasks (more to come, proposed by tarek):
- Make Distribute PEP 345 compatible
- Add a sandbox tool in Distutils2
- Write a distutils -> distutils2 converter
- Make virtualenv install Distutils2
Other possible things:
- Work on pypi (Mathieu Leduc-Hamel)
Tasks proposed by Martin v. Löwis
- Implement support for PEP 381 in distribute and setuptools:
- detect networking issues with pypi.python.org, by means of outright networking errors and timeouts.
- integrate a fallback algorithm, perhaps based on a randomized order My current proposal is that the mirrors are called [bcde...].mirrors.pypi.python.org (maybe this can be shortened to [bcde...].pypi.python.org); a.mirrors is PyPI itself. If there is a desire to find out what mirrors exist, I could also provide last.mirrors, pointing (by cname) to the alphabetically last mirror.
- try connecting to the mirror, expecting networking problems again.
- validate consistency of the mirror. There are multiple levels of that, e.g a) look whether last-modified is reasonably current b) validate the signature on each page being downloaded c) validate the md5sum of each file being downloaded.
- support serverkey rollover
- other PyPI issues
Development workflow:
- read the Hitchhiker’s Guide to Packaging
- fork the project at bitbucket
- ask for a pull request once the feature is done
- for distribute, switch to the `0.6-maintenance` branch
Montreal Python branches:
