You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One way would be to build the package wheel and push into PyPI and refer that wheel in both, but that increases my process to keep building and pushing new versions, and really defeating the purpose of referring to git revisions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Project structure:
Now I've Docker multi-stage builds on project A, where I compile the package dependencies into wheel files and pass the wheel files to run stage
When trying to install the packages at run stage I run into a dependencies conflict issue
The user requested
package2
1.0.0 (from /wheels/package2-1.0.0-py3-none-any.whl)package1
1.0.0 depends onpackage2
1.0.0 (from git+https://github.com/org/package2.git@abcde)Possible solution:
One way would be to build the package wheel and push into PyPI and refer that wheel in both, but that increases my process to keep building and pushing new versions, and really defeating the purpose of referring to git revisions.
Any other thoughts?
Beta Was this translation helpful? Give feedback.
All reactions