Open fridex opened 2 years ago
/assign @fridex to refine a bit more, especially by providing a list of acceptance criteria referencing all the parts/components that would be impacted
/triage needs-information
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
/remove-lifecycle rotten /sig stack-guidance /priority backlog
/good-first-issue
@mayaCostantini: This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
/triage accepted /priority important-soon
this might help: https://dephell.readthedocs.io/
I think we should turn this into a tracker issue, and open an issue on each of our repositories we care about. The individual tasks are not hard, but it's take time. This is typically the type of stuff which could be done in hacktoberfest, but for that we need to break it up into manageable chunks, and per repo seems the easiest.
I can script the issue creation without too much trouble I think.
@goern
I can script the issue creation without too much trouble I think. @goern
please go ahead :)
For now I put repos with a setup.py and no pyproject.toml. There is other (both presents for example), but that should the easiest ones.
If someone can add this to the issues desc...
Might be relevant (possible way to script the translation): https://stackoverflow.com/a/73830494
Is your feature request related to a problem? Please describe.
As Thoth, I would like to get rid of setuptools and start using pyproject.toml-based projects as that's how Python community is shifting.
Acceptance criteria