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

Add tox envs for building dists via PEP 517 #647

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
__author__ = 'Abhinav Singh'
__author_email__ = '[email protected]'
__homepage__ = 'https://github.com/abhinavsingh/proxy.py'
__download_url__ = '%s/archive/master.zip' % __homepage__
__download_url__ = '%s/archive/develop.zip' % __homepage__
Copy link
Owner

Choose a reason for hiding this comment

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

How I manage releases currently:

  1. Release happen from master branch
  2. Develop is used for cutting edge version

At some point, I'll create a PR from develop -> master, which contain all changes between pip releases.

I ideally don't recommend folks to install from develop, if they are looking for stability. Even though develop is tested and I use to everyday locally, it may contain untested code.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, I didn't realize. I thought maybe you forgot to update this.

__license__ = 'BSD'

if __name__ == '__main__':
Expand Down