Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Linting on temporary files means imports don't work #23

Closed
dmnd opened this issue Dec 5, 2014 · 5 comments
Closed

Linting on temporary files means imports don't work #23

dmnd opened this issue Dec 5, 2014 · 5 comments
Labels

Comments

@dmnd
Copy link
Member

dmnd commented Dec 5, 2014

You can get around this problem by adding a pylintrc file, though it's annoying to do for every project:

[MASTER]
init-hook='sys.path.insert(0, '.')'

I suspect this wouldn't be necessary if we linted actual files instead of temporary ones.

I think using temporary files for linter is problematic. Maybe we should stop doing that, and drop support for lint on change.

@hd-deman
Copy link
Member

hd-deman commented Dec 5, 2014

we can disable lint on change for some linter, but not drop support this on base linter.

@dmnd
Copy link
Member Author

dmnd commented Dec 5, 2014

@hd-deman I was writing steelbrain/linter#282 with the same idea as you wrote that. Let's discuss options in the base linter.

@SpainTrain
Copy link
Member

I believe that #55 fixes this issue. Please feel free to test and validate this is true.

@SpainTrain
Copy link
Member

Should be closed in the latest release (sans relative imports, see #58). @dmnd mind closing this if this is true?

@steelbrain
Copy link
Contributor

@SpainTrain can you contact me in #atom of atom slack please?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants