-
Notifications
You must be signed in to change notification settings - Fork 404
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
Proposal to change stdlib and mapping file formats. #76
Comments
I'm open to suggestions how the structure should look like :) |
Here's some suggestions and example usage. Personally, I'm more fond of the stdlib example 2 than example 1.
|
Your mappings structure looks solid, would definitely implement that. Your stdlib second example is also quite nice, but I don't exactly like the idea of storing duplicates for both versions, because most of the std libs are the same for python2 and 3. Perhaps we can have a general array of stdlib that work for python 2 and 3 and then extend that array with python specific version. So basically if a package is python 2 only, then it is present only in the python 2 set, if the package is available for python 2 and 3, then it is stored in the "general" set, and the same goes for python3 only packages. Other than that, looks good. |
Building on PR #75:
This would exclude modules based on python version, while keeping a general set in the first place. |
The current formats of
stdlib
andmapping
aren't very flexible, changing them to something more suitable like JSON or python dictionary would make them more flexible. This change would make it easier to include and exclude certain modules based on python version, and provide simple fixes to issues such as #61, #62 and #74.The text was updated successfully, but these errors were encountered: