[Python-Dev] accept the wheel PEPs 425, 426, 427 (original) (raw)
Daniel Holth dholth at gmail.com
Sat Oct 20 13:34:08 CEST 2012
- Previous message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Next message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The troublesome Description: parses fine -- as long as there is anything but a \r\n - for example "\r\n " - on successive blank lines. This tends to happen already.
Another solution comes to mind. Put the description in the payload. The description can have any form, and the installer can stop parsing at the first linesep pair because it only inspects Name, Version, and requirements. A little bit of a pain because you might have to also allow the description in the headers or rewrite it on install.
Metadata-Version: 1.3 Name: package Version: 0.13.0 Summary: A package. Classifier: Development Status :: 3 - Alpha Classifier: Intended Audience :: Developers Classifier: Programming Language :: Python Classifier: Programming Language :: Python :: 2 Classifier: Programming Language :: Python :: 2.7 Classifier: Programming Language :: Python :: 3 Classifier: Programming Language :: Python :: 3.3
Wheel
A built-package format for Python.
A wheel is a ZIP-format archive with a specially formatted filename and the .whl extension. It is designed to contain all the files for a PEP 376 compatible install in a way that is very close to the on-disk format. Many packages will be properly installed with only the "Unpack" step (simply extracting the file onto sys.path), and the unpacked archive preserves enough information to "Spread" (copy data and scripts to their final locations) at any later time.
- Previous message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Next message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]