Consider pep8 style for being the default about flake8-import-order

[pgjones]

I think this probably makes sense now the project is part of PyCQA, although I suspect it would break a many workflows.
My preference is to change the default, although I'd like others to comment before acting.

[sigmavirus24]

On June 26, 2016 11:10:16 AM CDT, Phil Jones [email protected] wrote:

I think this probably makes sense now the project is part of PyCQA,

Membership doesn't mean anything other than extra help with maintenance. :)

although I suspect it would break a many workflows.

That would make me biased against changing it, personally.

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[johnthagen]

An option could be to make the change and release it as a new major version (1.0?) to indicate that a backwards incompatible change have been made.

If accepted I'm also happy to submit a PR to update the code and docs.

[sigmavirus24]

get an out-of-the-box experience that they might expect

I'm not sure I agree with this sentiment. Before Flake8 itself started using flake8-import-order, I took a close look at the plugin, read what you read about cryptography import style and provenance and the other import styles. I then configured appropriately after installing it and experimenting with it. Maybe I'm atypical, but the project name isn't pep8-import-order, it's flake8-import-order. There's no implication that you're following PEP-0008 import style guide just because of "Flake8" (at least not to me). There are too many other projects/plugins prefaced with "flake8-" for there to be any implication of "PEP-0008-ness" in any of them.

[pgjones]

Given the comments here I think it is best to keep the default as cryptography. Overall I think the benefit of changing is unlikely to outweigh the cost.