-
Notifications
You must be signed in to change notification settings - Fork 2
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Suggestion for terminology "once-compatible" packages #4
Comments
I like the story-like connotations of 'once', but I wonder if 'previously' might be clearer to non-native speakers. |
We should certainly explain the term before we begin using it, in any case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The term would refer to packages that at one time were compatible with Python 2 and Python 3, that are migrating to Python 3 only compatibility in a new release.
Basically, this is the specific use case that this is trying to address.
Also, (bonus, not a reason per se) it carries a nice allusions to other Arthurian tales (specifically, The Once and Future King).
The text was updated successfully, but these errors were encountered: