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

Decouple Build Process from PyPI #275

Open
jjacobson95 opened this issue Dec 18, 2024 · 2 comments
Open

Decouple Build Process from PyPI #275

jjacobson95 opened this issue Dec 18, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@jjacobson95
Copy link
Collaborator

The build_all.py script currently includes:

  • building all datasets
  • pushing to Figshare
  • pushing to GitHub
  • pushing to PyPI

We want to decouple the PyPI build and have the ability to run this separately.

@jjacobson95 jjacobson95 added the enhancement New feature or request label Dec 18, 2024
@ymahlich
Copy link
Collaborator

It would be good to get a list of "interaction" points where the package relies on data that has been generated during the dataset build process (e.g. the figshare link).

We might want to have a "central" yaml or config file that contains all the information that is changed from version to version respectively the "hard coded" data that can change between build processes.

@jjacobson95
Copy link
Collaborator Author

The only interaction points are the figshare link, version/tag number (previously), and scripts/push_to_pypi.py (also no longer needed, but take a look).

I think the central yaml is a good idea. Want to create an issue for that separately?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants