-
Notifications
You must be signed in to change notification settings - Fork 422
Add a meta testenv for metadata: style & packaging #127
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
Conversation
The Travis CI build failure is actually spurious: https://travis-ci.org/pyca/pyopenssl/jobs/27969282#L890 Looks like it's probably actually something to do with the ASN1 mask change in #129? I'll add the meta testenv to the Travis build configuration. |
Okay, so just adding a meta testenv to the Travis build configuration won't work so easily. The Fortunately, all Python versions are actually always available in Travis builders; IIUC the main effect of the
...and then use
So, I suggest moving |
This would mean lots of changes, so I'm going to do them in separate PRs. |
More or less the |
Thanks, @dstufft :) I'll push the commits I'm working on here so you get an idea what I'm doing with the travis.yml, but FWIW this shouldn't be considered for merging right now until I get those other smaller PR's landed :) |
Conceptually we should review this and see what has already been done and what we need in 0.16. I'll add this to the milestone. |
rebase time! 💃 |
Do we want to keep them in one env? Is that to save time? |
@hynek Yep, that's why. |
You don’t have to pin the tools btw, if they break we wanna know. |
I've merged forward and removed the irrelevant pinnings. |
Please note that it does find some (alleged) problems:
|
3 similar comments
thanks coveralls |
It returns 0 on success, 1 on incorrect options and 2 if the rating is below 8. Our rating is 9, which is apparently Good Enough(TM). Alas, there doesn't appear to be an option to customize that... |
So two thoughts:
Cc @alex and @reaperhulk I guess. (I would also love to change the empty line rule to PEP8 but baby steps) |
I like using |
pyroma and flake8 check different things, no? pyroma is about packaging quality, flake8 is about code quality. They appear orthogonal. |
yeah flake8 is just pyflakes + pep8 + mccabe. pyroma is definitely orthogonal. |
Yes, flake8 was intended instead of pyflakes, not pyroma. Sorry for being ambiguous. |
so to be clear: I think pyroma should not be in |
OK. I will remove pyroma from allow_failures and use flake8 instead of pyflakes. |
w00t! Last step: we need to add [flake8]
ignore = 303 to setup.cfg to ignore “too many blank lines” which are currently on purpose. Any other suggestions that should be added? Thanks Laurens for bearing with me. :) |
done |
long lines aren’t fine but that’s fortunately not what 303 means ;) waiting for Travis now, thanks <3 |
1 similar comment
1 similar comment
|
Damit, it has to be |
done |
2 similar comments
Add a meta testenv for metadata: style & packaging
thanks, let’s finish this clusterfuck until I get some insane ideas :) |
revert merge button watching intensifies |
This adds some features for tox to test some meta stuff about PyOpenSSL. Specifically:
This isn't ready to be merged. It fails, and not as a false positive: MANIFEST.in is incomplete, and there's a few pyflakes warnings. I'm happy to do these on this PR, or on separate PRs.