[Python-Dev] BDFL delegation for PEP 426 (PyPI metadata 1.3)
Marcus Smith
qwcode at gmail.com
Sun Feb 3 21:16:18 CET 2013
More information about the Python-Dev mailing list
Sun Feb 3 21:16:18 CET 2013
- Previous message: [Python-Dev] BDFL delegation for PEP 426 (PyPI metadata 1.3)
- Next message: [Python-Dev] BDFL delegation for PEP 426 (PyPI metadata 1.3)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> The pip integration is basically to allow pip to find wheels on PyPI > or any local indexes you have, and to install them via the "pip > install" command. it also offers "pip wheel" for building wheels (using bdist_wheel) locally for your requirements, since wheels wouldn't be pervasive on PyPI for a while so, let's say you have a large app that has a requirements file, that ultimately installs 90 packages. run: pip wheel --wheel-dir=/my_wheels -r requirements.txt this will produce 90 wheel archives in a local directory, that you can then install against. Marcus -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130203/58e7dc72/attachment.html>
- Previous message: [Python-Dev] BDFL delegation for PEP 426 (PyPI metadata 1.3)
- Next message: [Python-Dev] BDFL delegation for PEP 426 (PyPI metadata 1.3)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list