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

config file is not used #564

Closed
keradus opened this issue Jul 26, 2016 · 5 comments
Closed

config file is not used #564

keradus opened this issue Jul 26, 2016 · 5 comments

Comments

@keradus
Copy link

keradus commented Jul 26, 2016

Hi!

I wanna switch to 2.0.0 version and I have some problems with it.

bin/pycodestyle --version
2.0.0

used config (from: https://pycodestyle.readthedocs.io/en/latest/intro.html#configuration)

vagrant@foo:/bar$ cat setup.cfg 
[pycodestyle]
max_line_length = 180

is not working.

when i change it into

vagrant@foo:/bar$ cat setup.cfg 
[pep8]
max_line_length = 180

it works.

why i need to use old name and not new one, as stated in docs ?

@sigmavirus24
Copy link
Member

This is a duplicate of #563 and #550. Please check open and closed issues before filing new ones.

@keradus
Copy link
Author

keradus commented Jul 26, 2016

as the bug is still not fixed on stable version I looked only on opened tickets.

any ETA about releasing the fix?

@sigmavirus24
Copy link
Member

as the bug is still not fixed on stable version I looked only on opened tickets.

Like most projects. Bugs are closed as they are fixed.

any ETA about releasing the fix?

I have none. @IanLee1521 performs releases. If he wants me to get 2.1.0 ready, though, I can.

@keradus
Copy link
Author

keradus commented Jul 26, 2016

Most projects keep the docs published for last stable release, not for next, not yet released ;)

Bugfix could go to PATCH version, so 2.0.1, if you don't want to create bigger release now.

One way or another thanks for guiding, I do appreciate it !

@sigmavirus24
Copy link
Member

Bugfix could go to PATCH version, so 2.0.1, if you don't want to create bigger release now.

Except that the next planned release is 2.1.0, although I don't suppose @IanLee1521 documents that anywhere.

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

No branches or pull requests

2 participants