User-specific config file #4815
Comments
|
This looks like a simple project which you can probably do yourself in a
few lines -- just submit a PR.
|
|
Sure! Happy to tackle it. |
OmeGak
added a commit
to OmeGak/mypy
that referenced
this issue
Apr 19, 2018
2 tasks
OmeGak
added a commit
to OmeGak/mypy
that referenced
this issue
Apr 19, 2018
OmeGak
added a commit
to OmeGak/mypy
that referenced
this issue
Apr 20, 2018
OmeGak
added a commit
to OmeGak/mypy
that referenced
this issue
Apr 20, 2018
OmeGak
added a commit
to OmeGak/mypy
that referenced
this issue
Apr 20, 2018
gvanrossum
pushed a commit
that referenced
this issue
Apr 21, 2018
|
Nice work @OmeGak Curious what your thoughts are on adding to this commit to support the XDG base directory specification? My home directory thanks you in advance 🙏 |
|
Not a strong opinion on XDG base directory. It wouldn't hurt complying with the specs, I guess. Maybe you could create a new issue proposing the idea for people to discuss it first? |
1 similar comment
|
Not a strong opinion on XDG base directory. It wouldn't hurt complying with the specs, I guess. Maybe you could create a new issue proposing the idea for people to discuss it first? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request. According to my search-fu, it hasn't been discussed yet.
mypywith no--config-filespecified will check formypy.inifirst, use tosetup.cfgotherwise, and ultimately fallback to the built-in defaults if none of them are present. I would like to have a user-default config that would be used instead. Would it be too crazy to check for~/.mypy.inibefore falling back to the built-in defaults?I would find this useful for quick prototyping without having to copy&paste my preferred configuration from other projects. It's also quite a common pattern in other static analysis tools like linters.
The text was updated successfully, but these errors were encountered: