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

Prune submodules and move packages to PyPi or conda. #1846

Open
litghost opened this issue Dec 4, 2020 · 6 comments
Open

Prune submodules and move packages to PyPi or conda. #1846

litghost opened this issue Dec 4, 2020 · 6 comments
Labels
cleanup help wanted

Comments

@litghost
Copy link
Contributor

litghost commented Dec 4, 2020

There are many submodules that right now only exist to be installed into the local python environment or to build binaries that exist in conda. Many can likely be changed to simply use the PyPi version or conda package once ready.
@litghost litghost added this to Needs triage in Code Health via automation Dec 4, 2020
@duck2
Copy link
Collaborator

duck2 commented Jan 22, 2021

I may give this a try. Do we only need to change submodule paths in requirements.txt to PyPI packages?

@litghost
Copy link
Contributor Author

I may give this a try. Do we only need to change submodule paths in requirements.txt to PyPI packages?

Depends. I think for some of them, we need to push the packages to PyPI, which is a little more work.

@litghost
Copy link
Contributor Author

litghost commented Jan 28, 2021 •
edited

Packages that should move to PyPi:

@mithro
Copy link
Contributor

mithro commented Jan 28, 2021 •
edited by unfurl-links bot

Documentation is at https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

@mithro
Copy link
Contributor

mithro commented Jan 28, 2021 •
edited

secrets.PYPI_TEST_PASSWORD should be available on any public repository for publishing to https://test.pypi.org/legacy/

@mithro
Copy link
Contributor

mithro commented Jan 28, 2021

Once we have it working, secrets.PYPI_PASSWORD can be used to publish to the real PyPi.

@litghost litghost mentioned this issue Feb 1, 2021
Closed
@kgugala kgugala removed this from Needs triage in Code Health Sep 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mithro @litghost @duck2