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

Tox improvements and added black as formatter #431

Merged
merged 16 commits into from Mar 5, 2021
Merged

Conversation

loechel
Copy link
Member

@loechel loechel commented Jun 17, 2019

No description provided.

@mister-roboto
Copy link

@loechel thanks for creating this Pull Request and help improve Plone!

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.

Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:

@jenkins-plone-org please run jobs

With this simple comment all the jobs will be started automatically.

Happy hacking!

Copy link
Sponsor Member

@mauritsvanrees mauritsvanrees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks roughly right.
Locally most jobs fail with an error like this:

Couldn't open .tox/py39-plone-5.2/plone-5.2.x.cfg

docs, isort and lint are the only three that pass.

BTW, I recently learned about tox -p auto to run tox in parallel. Saves a lot of time.

loechel and others added 7 commits January 31, 2021 20:55
The code might still work, but it is no longer tested.
You can use releases in the 1.10 series on the older versions.
Theoretically our tests might work, but there is definitely other code that would have test failures,
so you should not use it on 5.2.
And no easy way to already test on 6.0.  But we have buildout.coredev and Jenkins.
mauritsvanrees and others added 4 commits March 1, 2021 11:45
I thought I did that already, but this was only in tox.ini.  It was still in the travis config.
Seems better, as the other envs at most use 3.8.
And on Travis the docs env fails, with no output.  Maybe this helps.
See also the closed PR #455 where I try a few Python versions and add some comments.
Further improvements to the tox PR
Copy link
Sponsor Member

@mauritsvanrees mauritsvanrees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@loechel I have merged my PR #453 into your PR branch. This drops Plone 4.3-5.1, as per discussion on #450.
Travis should be green now. For me this is good to merge to master.

@mauritsvanrees
Copy link
Sponsor Member

Travis should be green by now, but let's not forget Jenkins:

@jenkins-plone-org please run jobs

@ale-rt
Copy link
Member

ale-rt commented Mar 5, 2021

@plone/framework-team I would say that given no one spoke against #450 since quite some days this is fine to merge

@loechel
Copy link
Member Author

loechel commented Mar 5, 2021

@ale-rt please feel free to merge

@ale-rt ale-rt merged commit bb92414 into master Mar 5, 2021
@ale-rt ale-rt deleted the tox-improvements+black branch March 5, 2021 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants