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

Finish migration to pyproject.toml #37

Merged
merged 2 commits into from
Apr 17, 2024

Conversation

venthur
Copy link
Contributor

@venthur venthur commented Sep 18, 2023

  • Removed setup.py and setup.cfg -- all their contents has been moved to pyproject toml.
  • don't use poetry but standard setuptools, we were not using any of poetries features so we can get rid of that dependency
  • put dev-dependencies into pyproject.toml and use that via pip install -e .[dev] instead of manually listing dependencies in github actions

* Removed setup.py and setup.cfg -- all their contents has been moved to
  pyproject toml.
* don't use poetry but standard setuptools, we were not using any of
  poetries features so we can get rid of that dependency
* put dev-dependencies into pyproject.toml and use that via pip install
  -e .[dev] instead of manually listing dependencies in github actions
@justinmayer justinmayer changed the title finished migration to pyproject.toml Finish migration to pyproject.toml Apr 17, 2024
Copy link
Member

@justinmayer justinmayer left a comment

Choose a reason for hiding this comment

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

Hi Bastian. Please accept my sincere apologies for the long delay in reviewing your thoughtful contribution. Your changes are great. I made a few minor tweaks while still keeping your core improvements intact. Many thanks for your work on this! 😁

@@ -46,7 +45,7 @@ jobs:
- name: Check release
id: check_release
run: |
python -m pip install poetry githubrelease httpx==0.18.2 autopub twine wheel
python -m pip install -e .[dev]
Copy link
Member

Choose a reason for hiding this comment

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

The general concept behind this makes sense and is an improvement in the test job, but for deployment I think it's better to install autopub[github] directly via the deploy job because these packages are only useful in the CI environment — there is no reason for individual developers to have these packages installed on their respective workstations.

@justinmayer justinmayer merged commit 44f2f92 into getpelican:main Apr 17, 2024
7 checks passed
@venthur
Copy link
Contributor Author

venthur commented Apr 18, 2024

All good! Thanks for maintaining feedgenerator!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants