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
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
What are you trying to do?
I am uploading a pip package (stored as a .whl/wheel locally) to an existing PyPi Nexus repository. The upload succeeds, but attempting to install pip packages from this repository fails because the uploaded wheel is zipped (into a .zip) somewhere in the upload process. I've been looking through this SDK's source and I don't see where it's zipping any component, so it must be the Nexus 3 backend zipping the file. Any advice on how to avoid this while uploading Python wheels?
What feature or behavior is this required for?
Component upload
How could we solve this issue? (Not knowing is okay!)
Help me figure out how to avoid the Nexus backend zipping the uploaded wheel file.
Anything else?
The text was updated successfully, but these errors were encountered:
Thanks for creating an issue! Please fill out this form so we can be
sure to have all the information we need, and to minimize back and forth.
What are you trying to do?
I am uploading a pip package (stored as a .whl/wheel locally) to an existing PyPi Nexus repository. The upload succeeds, but attempting to install pip packages from this repository fails because the uploaded wheel is zipped (into a
.zip
) somewhere in the upload process. I've been looking through this SDK's source and I don't see where it's zipping any component, so it must be the Nexus 3 backend zipping the file. Any advice on how to avoid this while uploading Python wheels?What feature or behavior is this required for?
Component upload
How could we solve this issue? (Not knowing is okay!)
Help me figure out how to avoid the Nexus backend zipping the uploaded wheel file.
Anything else?
The text was updated successfully, but these errors were encountered: