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

isort silently writes output to the current directory, even if run on a different path #15

Closed
vmalloc opened this issue Sep 8, 2013 · 2 comments
Labels
bug Something isn't working

Comments

@vmalloc
Copy link

vmalloc commented Sep 8, 2013

It seems like the tool always writes the result into the current directory, which is pretty unexpected. I think you should provide an --inplace option or fail explicitly if you don't know where to save the result.

Currently for the unsuspecting newcomer it seems that the tool does nothing when run on a different path.

@timothycrosley
Copy link
Member

Thanks for finding this problem! Just verified it as an issue and will fix with the next point release.

@timothycrosley
Copy link
Member

Fixed with release 1.2.3: we can always determine the correct output file using os.path.abspath, and then isort subdirectory/pythonfile.py works as expected.

Thanks!

Timothy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants