We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
You know what?
from os import path2 as path
is not cool enough. Maybe:
from os.path2 import path
instead?
what would require some changes in our .pth file but it's possible
The text was updated successfully, but these errors were encountered:
I really like this. Import is no cool, but is suggesting a lot. path2 is a replacement for path and it should as close as possible to
from os import path
I think every day usage will be
from os import path2
On Sat, Jun 15, 2013 at 1:06 AM, Kuba Janoszek [email protected]:
You know what? from os import path2 as path is not cool enough. Maybe: from os.path2 import path instead? what would require some changes in our .pth file but it's possible — Reply to this email directly or view it on GitHubhttps://github.com//issues/3 .
— Reply to this email directly or view it on GitHubhttps://github.com//issues/3 .
Sorry, something went wrong.
No branches or pull requests
You know what?
is not cool enough. Maybe:
instead?
what would require some changes in our .pth file but it's possible
The text was updated successfully, but these errors were encountered: