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

Source distribution via Travis #356

Merged
merged 3 commits into from
Oct 19, 2018
Merged

Source distribution via Travis #356

merged 3 commits into from
Oct 19, 2018

Conversation

KeyWeeUsr
Copy link
Contributor

Since the default setup.py already does various stuff and there are multiple platforms to support, source dist is easy fix until someone might find interesting to do binary dist. I put the sdist into a separate file with some default common values in a dictionary to reuse them in both setup files.

On Travis the build is set up, so that when $PYJNIUS_DEPLOY == 1 it builds the source distribution and attempts to upload it to PyPI(currently test server via Travis settings).

pip install pyjnius --index-url https://test.pypi.org/simple/

cmdclass={'build_ext': build_ext},
packages=['jnius'],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does removing all the keys here still work when building -not- source releases? I don't understand the point to create a separate sdist setup

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sdist means we don't create any wheels, we just release it the same way you can install it from GitHub:

pip install https://github.com/kivy/pyjnius/zipball/master

and separating the keys means I can safely create the source archive and upload it to PyPI with all the classifiers and other metadata in tact. Also it means a GNU/Linux user can install it from PyPI the same way eg. Cython is installed on RPi - compilation is triggered.

It can compile the normal way and even via pip if you run the command from above.

Log:

https://travis-ci.org/kivy/pyjnius/jobs/441130344#L624

@tito
Copy link
Member

tito commented Oct 19, 2018

Could you fix the conflict?

tito
tito previously approved these changes Oct 19, 2018
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.

2 participants