Python Package

[undu]

This makes sequestrum installable using pip, and friendlier to distro packagers.

[buffet]

Also:

• Added .gitignore
• Restructed a little (source -> sequestrum)

[undu]

The second is a necessity for having a python package with an executable :)

[buffet]

@undu I figured later. I normally don't do python, just wanted to be helpful.

[buffet]

Would fix #2

[iyzg]

Hey @undu! Thanks so much for contributing, and this is actually awesome! Could you fix the conflicts and then I'l merge it into master. Hopefully I fix the structure soon and you can just merge to the develop branch next time. Have a good day!

[undu]

I took the liberty to fix a colon and using a function that doesn't exist in the code, you might want to run pylint or any other linter that tells you about these kinds of mistakes before committing them ;)

[iyzg]

OMG... I'm so sorry 😭 Didn't realize my linter was off. Thanks so much man!

[iyzg]

@undu Hey.... so how are users supposed to use pip to install this? I've personally never used pip before in a project xD

[undu]

• First thing is building the package:
  python setup.py bdist_wheel
  Before doing so you may want to add more information about python compatibility in setup.py. For example: https://github.com/undu/tox-path-example/blob/master/setup.py

List of valid classifier values: https://pypi.org/pypi?%3Aaction=list_classifiers

• Second uploading to pypi using twine:
  twine upload dist/*

You can check instructions in the twine link to upload to the test pypi before making the actual upload.

• Then the user can install it with pip: pip install sequestrum

Alternatively people can download the source, create the package from the first step and install it from the package (wheel):
pip install <sequestrum-version>.whl

PS: The version of the package generated is taken from the git tag; I recommend to publish only packages taken from tagged commits, otherwise they'll contain the hash of the git commit they're based in.

[buffet]

@undu He's already working on switching to a Git Flow workflow, which would allow to work with tagged releases on the master branch.

[iyzg]

Alright thanks so I should only push to GitHub and upload to pip the releases that have a tag? I'll upload to pip tonight after making a tagged release just so I can put it on there. Much thanks c:

[undu]

The release process would be:

• Prepare readmes, changelogs, etc
• Tag the commit in git (also upload it to github)
• Make the package from the tagged commit & upload

[iyzg]

Thanks so much!

[iyzg]

Hey @undu I've been trying to upload a new version but it's giving me

HTTPError: 400 Client Error: File already exists. See https://pypi.org/help/#file-name-reuse for url: https://upload.pypi.org/legacy/

I've been doing

1. git add .
2. git commit -m "Some Message
3. git tag <tagname>
4. git push origin <tagname>

Then i've been doing the steps you said up there, but it isn't uploading. If you could help that'd be awesome. Thanks c:

[iyzg]

twine upload -r pypi dist/sequestrum-<version_number>*
python setup.py sdist bdist_wheel

Find version number in dict
This is what I had to do to fix it and have it uplaod the correct file.