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.

Sign up for GitHub

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

Jump to bottom

Make ansys-advanced/pyprojec.toml PEP 621 compliant #48

Open
jorgepiloto opened this issue Apr 4, 2022 · 1 comment
Open

Make ansys-advanced/pyprojec.toml PEP 621 compliant #48

jorgepiloto opened this issue Apr 4, 2022 · 1 comment
Labels
enhancement New features or code improvements

Comments

@jorgepiloto
Copy link
Member

🐞 Problem

Similar situation as in #46. Duplicated instances of pyproject.toml for the build-system tools flit and poetry.

💡 Solution

Combine those into a single file.
@jorgepiloto
Copy link
Member Author

Important: PEP 621 – Storing project metadata in pyproject.toml

In essence, previous pep tries to unify the way metadata is specified in the pyproject.toml file independently from the build-system being used.

However, it looks like poetry has not yet implemented this, see the following issues:

This was referenced Apr 7, 2022
Closed
Merged
@jorgepiloto jorgepiloto changed the title Unify pyansys_advanced pyproject_*.toml files Make ansys-advanced/pyprojec.toml PEP 621 compliant Apr 7, 2022
@jorgepiloto jorgepiloto added the enhancement New features or code improvements label Apr 18, 2022
@github-actions github-actions bot removed the blocked label May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New features or code improvements
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jorgepiloto