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

Systematic tagging of new releases and upload to PyPI #110

Closed
ghisvail opened this issue Apr 12, 2017 · 1 comment
Closed

Systematic tagging of new releases and upload to PyPI #110

ghisvail opened this issue Apr 12, 2017 · 1 comment

Comments

@ghisvail
Copy link

Please consider systematically tagging and releasing tarballs to PyPI in the future. Neither 1.2.11, 1.2.12, 1.3.0 and now 1.4.0 were tagged nor pushed to PyPI which makes tracking of new releases downstream more difficult than it should be. Right now, anything requiring pbcore would still download the outdated 1.2.10 version from PyPI.

Thanks,
pacbbbbot pushed a commit that referenced this issue Sep 27, 2018
@mdsmith
Merge pull request #110 in SAT/pbcore from feature/SE-2004-pbcore-s-d…
394e6bc 
…atasets-should-write-to to develop

* commit '21381b843138b9efb675e417bea52136579d908e':
  Fix issue with unicode filenames
@pb-dseifert
Copy link
Contributor

For legal reasons we dont upload releases to PyPI anymore. If you'd like to use pbcore, please use it via Bioconda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ghisvail @pb-dseifert