Differences between revisions 24 and 25
Revision 24 as of 2005-03-22 19:10:54
Size: 4049
Editor: FredDrake
Comment:
Revision 25 as of 2008-11-15 14:00:33
Size: 4059
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 * The implementation of [http://www.python.org/peps/pep-0314.html PEP 314: Metadata for Python Software Packages v1.1] should be complete; someone who isn't involved in the implementation should review what's in CVS and check it against the PEP. Work performed at the sprint included supporting the ''provides'', ''requires'', and ''obsoletes'' metadata fields in both the {{{distutils}}} package and in PyPI. The work was performed by FredDrake, RichardJones, and AndyHarrington. There may be some untracked changes in AndrewKuchling's draft of PEP 314; these should also be checked (also, the catalog-sig archives). FredDrake believes that there are still some glaringly obvious metadata fields missing, necessitating a further revision of the package metadata specification.  * The implementation of [[http://www.python.org/peps/pep-0314.html|PEP 314: Metadata for Python Software Packages v1.1]] should be complete; someone who isn't involved in the implementation should review what's in CVS and check it against the PEP. Work performed at the sprint included supporting the ''provides'', ''requires'', and ''obsoletes'' metadata fields in both the {{{distutils}}} package and in PyPI. The work was performed by FredDrake, RichardJones, and AndyHarrington. There may be some untracked changes in AndrewKuchling's draft of PEP 314; these should also be checked (also, the catalog-sig archives). FredDrake believes that there are still some glaringly obvious metadata fields missing, necessitating a further revision of the package metadata specification.
Line 13: Line 13:
 * RichardJones and MartinvonLoewis worked on implementing [http://www.python.org/peps/pep-0243.html PEP 243: Module Repository Upload Mechanism], supporting a package repository as part of PyPI. There are revisions needed to PEP 243 which haven't been written yet (mostly to do with cleaning up the use of the HTTP spec). FredDrake thinks he uploaded the first package into the live repository, a tarball containing ZConfig 2.2. Richard implemented the changes to the PyPI application, and Martin added an '''upload''' command to the {{{distutils}}} package to make it easy to add files from a command line. Uploads may also have an accompanying MD5 (for simple validation) and OpenPGP signature.  * RichardJones and MartinvonLoewis worked on implementing [[http://www.python.org/peps/pep-0243.html|PEP 243: Module Repository Upload Mechanism]], supporting a package repository as part of PyPI. There are revisions needed to PEP 243 which haven't been written yet (mostly to do with cleaning up the use of the HTTP spec). FredDrake thinks he uploaded the first package into the live repository, a tarball containing ZConfig 2.2. Richard implemented the changes to the PyPI application, and Martin added an '''upload''' command to the {{{distutils}}} package to make it easy to add files from a command line. Uploads may also have an accompanying MD5 (for simple validation) and OpenPGP signature.
Line 15: Line 15:
 * AndrewKuchling integrated work done to add XML-RPC support based on efforts from the ChiPy sprint. See [http://blog.ianbicking.org/first-chipy-sprint-pypi.html Ian Bicking's blog] for more on the ChiPy work.  * AndrewKuchling integrated work done to add XML-RPC support based on efforts from the ChiPy sprint. See [[http://blog.ianbicking.org/first-chipy-sprint-pypi.html|Ian Bicking's blog]] for more on the ChiPy work.
Line 23: Line 23:
 * Phillip Eby brought up the idea of application plugins; it would be really nice to see this happen. He and Bob Ippolito have some [http://peak.telecommunity.com/DevCenter/PythonEggs design notes] and Bob Ippolito has begun an implementation of the runtime. In addition to plugins, this "Python Egg" format should be useful for distributing libraries and building applications (via py2exe/py2app) as well.  * Phillip Eby brought up the idea of application plugins; it would be really nice to see this happen. He and Bob Ippolito have some [[http://peak.telecommunity.com/DevCenter/PythonEggs|design notes]] and Bob Ippolito has begun an implementation of the runtime. In addition to plugins, this "Python Egg" format should be useful for distributing libraries and building applications (via py2exe/py2app) as well.
Line 28: Line 28:
 * Installing large applications; see [http://mail.python.org/pipermail/distutils-sig/2005-February/004389.html Fred's post to the Distutils-SIG] for more on this topic.  * Installing large applications; see [[http://mail.python.org/pipermail/distutils-sig/2005-February/004389.html|Fred's post to the Distutils-SIG]] for more on this topic.

Schedule

FredDrake suggested we start at 10:00am, at least on Saturday and Sunday, but apparantly others were better able to rise in the mornings. The DistutilsSprint was held in room 301 at the conference center.

Topics

Some projects which saw progress during the sprint included:

  • The implementation of PEP 314: Metadata for Python Software Packages v1.1 should be complete; someone who isn't involved in the implementation should review what's in CVS and check it against the PEP. Work performed at the sprint included supporting the provides, requires, and obsoletes metadata fields in both the distutils package and in PyPI. The work was performed by FredDrake, RichardJones, and AndyHarrington. There may be some untracked changes in AndrewKuchling's draft of PEP 314; these should also be checked (also, the catalog-sig archives). FredDrake believes that there are still some glaringly obvious metadata fields missing, necessitating a further revision of the package metadata specification.

  • RichardJones migrated the database away from the single-user sqlite database to a multi-user postgres one.

  • RichardJones and MartinvonLoewis worked on implementing PEP 243: Module Repository Upload Mechanism, supporting a package repository as part of PyPI. There are revisions needed to PEP 243 which haven't been written yet (mostly to do with cleaning up the use of the HTTP spec). FredDrake thinks he uploaded the first package into the live repository, a tarball containing ZConfig 2.2. Richard implemented the changes to the PyPI application, and Martin added an upload command to the distutils package to make it easy to add files from a command line. Uploads may also have an accompanying MD5 (for simple validation) and OpenPGP signature.

  • AndrewKuchling integrated work done to add XML-RPC support based on efforts from the ChiPy sprint. See Ian Bicking's blog for more on the ChiPy work.

  • RichardJones and MichaelTwomey integrated work started at the ChiPy sprint to convert the PyPI web interface to use ZopePageTemplates instead of hard-coded HTML in the Python code. This should make it a lot easier to keep the logic and presentation separate. "Unit" tests using Selenium were also developed.

  • JohnCamara worked on some distutils bugs, and also implemented the ReStructuredText formatting of description fields. DavidGoodger implemented a couple of safety switches in docutils allowing us to turn off the "raw" and "include" directives.

At a separate table in the other sprint room, this suggested topic was addressed:

  • Phillip Eby brought up the idea of application plugins; it would be really nice to see this happen. He and Bob Ippolito have some design notes and Bob Ippolito has begun an implementation of the runtime. In addition to plugins, this "Python Egg" format should be useful for distributing libraries and building applications (via py2exe/py2app) as well.

The following topics had been suggested, but were not discussed during the [PyConDC2005/Sprints]:

  • Installing large applications; see Fred's post to the Distutils-SIG for more on this topic.

  • Defining a way to define new classes of files that can be installed. Zope 3 would like this for the "package-includes" files we use; it's likely generally useful.

Participants

If you aren't planning to be available for all four days of the sprints, please note which days you will be around.


CategoryPyCon2005

DistutilsSprint (last edited 2015-01-10 12:12:10 by WolfgangMaier)

Unable to edit the page? See the FrontPage for instructions.