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.

Sign up for GitHub

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

Jump to bottom

project level configuration (something that can be checked into git) #53

Closed
graingert opened this issue Oct 20, 2013 · 4 comments
Closed

project level configuration (something that can be checked into git) #53

graingert opened this issue Oct 20, 2013 · 4 comments
Labels
enhancement New feature or request
Milestone
2.3.0

Comments

@graingert
Copy link
Member

I'm working on a project with some funky paths config, which means the project I'm working on is discovered as a thirdy-party lib rather than first-party code.

It would be nice to have a config file ala .pep8 or setup.cfg that can be checked into git.
@graingert
Copy link
Member Author

maybe for each file given to isort recurse up the file-system until you hit the first .isort.cfg? Then fall-back to ~/.isort.cfg

@timothycrosley
Copy link
Member

Agreed! Will get this in for the next release.

@graingert
Copy link
Member Author

👍

timothycrosley added a commit that referenced this issue Oct 26, 2013
@timothycrosley
Add initial support for project level configs, fixing issue #53
d66b837
@timothycrosley
Copy link
Member

Implemented and dev and documented here: https://github.com/timothycrosley/isort#configuring-isort will go live with the next release :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
2.3.0
Development

No branches or pull requests
2 participants
@graingert @timothycrosley