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

feature requests - envs provided by plugins #828

Open
RonnyPfannschmidt opened this issue May 24, 2018 · 2 comments
Open

feature requests - envs provided by plugins #828

RonnyPfannschmidt opened this issue May 24, 2018 · 2 comments
Labels
feature:change something exists already but should behave differently help:wanted Issues that have been acknowledged, a solution determined and a PR might likely be accepted. level:hard rought estimate that this might be quite hard to implement needs:discussion It's not quite clear if and how this should be done

Comments

@RonnyPfannschmidt
Copy link

there are common tasks like linting, chdechecks, and it would be nice if it was possible to move them to some kind of env or plugin

the use case that brought this uppon was switching the linting of pytest to pre-commit, and realizing that pretty much all pre-commit using projects are would need the same tox.ini entry to map linting to pre-commit

@obestwalter obestwalter added needs:discussion It's not quite clear if and how this should be done feature:new something does not exist yet, but should labels May 24, 2018
@gaborbernat
Copy link
Member

A plugin to have the ability to create a new environment I believe is a reasonable requirement. My sole requirement for an implementation of this is to keep the entire tox configuration explicit (in the spirit of the Python Zen). Therefore, any solution of this first would need to start with adding plugin requirements. Lacking a plugin required for that project would fail the tox build.

@gaborbernat gaborbernat added level:medium rought estimate that this might be neither easy nor hard to implement level:hard rought estimate that this might be quite hard to implement and removed level:medium rought estimate that this might be neither easy nor hard to implement labels May 24, 2018
@gaborbernat
Copy link
Member

The plugin requires format has been implemented. Now we just need to create some example plugins.

@gaborbernat gaborbernat added this to the 3.5 milestone Sep 18, 2018
@gaborbernat gaborbernat modified the milestones: 3.5, 3.6 Oct 8, 2018
@gaborbernat gaborbernat modified the milestones: 3.6, 3.7 Dec 16, 2018
@gaborbernat gaborbernat added feature:change something exists already but should behave differently help:wanted Issues that have been acknowledged, a solution determined and a PR might likely be accepted. and removed feature:new something does not exist yet, but should labels May 3, 2019
@gaborbernat gaborbernat modified the milestones: 3.7, 4.0 Jan 13, 2022
@gaborbernat gaborbernat modified the milestones: 4.0, 4.1 Nov 20, 2022
@gaborbernat gaborbernat removed this from the P-1 milestone Jun 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:change something exists already but should behave differently help:wanted Issues that have been acknowledged, a solution determined and a PR might likely be accepted. level:hard rought estimate that this might be quite hard to implement needs:discussion It's not quite clear if and how this should be done
Projects
None yet
Development

No branches or pull requests

3 participants