Skip to content

Added pypi instructions#14

Merged
tzach merged 2 commits intoscylladb:masterfrom
dgarcia360:pypi-instructions
May 20, 2020
Merged

Added pypi instructions#14
tzach merged 2 commits intoscylladb:masterfrom
dgarcia360:pypi-instructions

Conversation

@dgarcia360
Copy link
Copy Markdown
Collaborator

Closes #10

@tzach tzach merged commit 8c44705 into scylladb:master May 20, 2020
@dgarcia360 dgarcia360 deleted the pypi-instructions branch May 20, 2020 09:01
@tzach
Copy link
Copy Markdown
Collaborator

tzach commented May 20, 2020

@dgarcia360 what the best practice in PyPy version?
Should we update it with every push?
If I do not update the version, does it override the package?

@dgarcia360
Copy link
Copy Markdown
Collaborator Author

@tzach To release a new version on PyPi, the version number needs to be increased. The package manager won't accept uploading a package with an existing version number.

I prefer to release a new version every time I decide to add a new release tag on GitHub. By doing so, the project does not burn a version number if the changes merged are too minimal, or if multiple PR should be combined / tested together before launching a new release.

Right now, the deployment to PyPi is done manually, but it could be automated. Once we complete the Python Driver automation project, we could work on the automation to deploy this package directly to PyPi when the repository is tagged. Please, let me know if this is interesting to open a new issue.

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.

Add instructions to push the theme into PyPy

2 participants