Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supported Python versions for an archive #51

Open
nir0s opened this issue Jul 6, 2016 · 3 comments
Open

Supported Python versions for an archive #51

nir0s opened this issue Jul 6, 2016 · 3 comments
Milestone

Comments

@nir0s
Copy link
Contributor

nir0s commented Jul 6, 2016

Currently, the supported python versions are either provided via user input or automatically deduced (as a single version) from the python version currently used to create the wagon.

  1. We should rethink allowing users to provide the versions. It might be irrelevant
  2. We should redo the mechanism which understands the python versions supported as the current one is technically not true. We might want to iterate through all wheels and get the set of common versions and use them instead.
@nir0s nir0s changed the title Supported Python versions Supported Python versions for an archive Jul 6, 2016
@nir0s
Copy link
Contributor Author

nir0s commented Nov 28, 2016

We should also check how wheel implements this and directly use its implementation if possible.

@nir0s
Copy link
Contributor Author

nir0s commented Jan 5, 2017

Looking at this, it seems like wheel's implementation is irrelevant here. Wheel's implementation simply takes the runtime env (ip, pp, py, etc..), appends the relevant python versions and uses it for a single wheel. The work to do here is to do cross-wheel version intersections. We'll leave it for 1.0.0 to focus on functionality first.

@nir0s nir0s added this to the v1.0.0 milestone Jan 5, 2017
@nir0s
Copy link
Contributor Author

nir0s commented Jan 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant