Wheelhouse Generation
See original GitHub issue- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
Hey Poetry Crew,
Given an enterprise python context, most devs are using private pypi registries to house/distribute their artifacts. In general, downloading artifacts from a custom registry requires a network configuration (VPN) and login credentials. While some companies have integrated their build/deploy pipelines with their custom registries, others are relying on the wheelhouse deployment approach (generate all the wheels locally and upload) to send their applications to the cloud.
Pip does support this with the pip wheel -i
command. Poetry could wrap around pips functionality to ensure hashes that are stored in the lock file are used while generating a wheelhouse for deployment. I made this SO post describing ONE potential scenario where this feature would be very useful.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (4 by maintainers)
This is how I’m currently solving it, but it means not using poetry for my actual final production install. I just use it in development and to track the locking:
@cpvandehey I am not entirely sure if this falls within the scope for poetry. If I am understanding you correct, you want all project dependencies downloaded into a local directory.
Wouldn’t something like this be sufficient?
Additional note, it might also make more sense to maybe support zipapp builds.