-
Notifications
You must be signed in to change notification settings - Fork 1
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
Deploy public-facing packages to pypi #13
Comments
There may be some useful GitHub actions steps you can run at the following link: https://py-pkgs.org/08-ci-cd#testing-continuous-deployment But maybe we want to do this from Jenkins This message comes from @robons |
csvqb, csvwlib-models, csvwlib-pmd, csvwlib-devtools are suggested names for the packages. |
Having done checks on pypi, the csvwlib name is taken by another utility. We are now at |
I do prefer |
Do you want to create a related issue to deal with renaming the repo and all references to csvwlib? |
Are we there on getting them to the public pypi instance yet? |
Cannot publish to pypi without making some modifications, which I did on the test-pypi publish. Your fork of pydantic, @robons, cannot be referenced directly via url to a GitHub repo.
I have changed the existing pydantic reference in csvcubed to pydantic proper, and published 0.1.0-rc1 on test-pypi for all four packages. I am holding off until we talk about it on the proper pypi. |
We can't make users pip install -e git+https://...
todo: Need to decide what our organisation's name on pypi should be - and which email address should we sign up under?
@canwaf knows all about how to name mailboxes, so he seems like the most suitable person to push this issue forwards. @JasonHowell may be required to support this too.
The text was updated successfully, but these errors were encountered: