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

Proposal: Removing --aggressive and --experimental option #422

Open
hhatto opened this issue Aug 30, 2018 · 2 comments
Open

Proposal: Removing --aggressive and --experimental option #422

hhatto opened this issue Aug 30, 2018 · 2 comments
Milestone

Comments

@hhatto
Copy link
Owner

hhatto commented Aug 30, 2018

Why?

The current -a, -aa, -aaa, --experimental option is confusing and becomes a factor to increase the maintenance cost. Delete these options and change them to control all operations with --select or --ignore.

migration plan

If you used -a option or --experimental option on the next minor release version of autopep8, it outputs a warning.
And remove the option with the next major update (v2.0).

I would like to hear your opinion.

Thanks.

@bigredengineer
Copy link
Contributor

👍 The best thing about the -a, -aa, etc options was that you can control several classes of operations easily. If the --select and --ignore contain some kind of grouping mechanism I would like the proposed change. As part of this, the documentation would need to be updated to better showcase how the operations are grouped together. Honestly, the documentation needs this anyway so it would be a good reason to dig into it.

@hhatto hhatto added this to the 2.0 milestone Jan 1, 2020
@hhatto hhatto pinned this issue May 25, 2020
@dougireton
Copy link

As someone new to AutoPEP8 I don't understand the aggressive options. I like the --select, --ignore options, but I really need more guidance. It'd be nice to have a table with a link to each pycodestyle rule and whether autopep8 will fix it by default or I need to add that rule to --select. Maybe sorting the table by default rules vs. non-default would help me focus in on the non-default rules to see which ones I wanted to include.

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

3 participants