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

IMP: transition to pyproject.toml #24

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from
Draft

Conversation

lizgehret
Copy link
Collaborator

Partially addresses #1 (sans documentation, will link PR once that's been added)

Couple of thoughts/notes (cc @gregcaporaso):

One thing we don't have in here is a templated meta.yaml file - I'm not sure if it makes sense to add that for a starter plugin over having folks actually create that file on their own. they won't necessarily need it unless they'd like to build their package using conda (which isn't necessary for the ci template i created for weekly builds, that just utilizes a pip install).

Another thing with these changes is that since we're no longer vendoring versioneer (which is why the top level versioneer.py file is gone) the plugin developer will need to have versioneer installed in whatever environment they're developing in (otherwise their package won't build successfully). I need to confirm that this will work with the spec in pyproject.toml but as long as that works, they shouldn't have to do anything extra on their end.

@lizgehret lizgehret linked an issue Aug 27, 2024 that may be closed by this pull request
@lizgehret lizgehret self-assigned this Aug 29, 2024
@gregcaporaso gregcaporaso marked this pull request as draft September 5, 2024 17:40
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.

transition from setup.py to pyproject.toml
1 participant