Skip to content

iesfausti/faustilib

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Create a new repository on the command line

touch README.md git init git add README.md git commit -m "first commit" git remote add origin https://github.com/iesfausti/faustilib.git git push -u origin master Push an existing repository from the command line

git remote add origin https://github.com/iesfausti/faustilib.git git push -u origin master

How to submit a package to PyPI

[Aclaracion] 1º .pypirc no lo crea bien, me lo salto y el me lo crea, luego lo retoco, donde? en HOME (variable a crear en windows para que en el cmd.exe lo encuentre) 2º usar pytest es mas politicamente correcto para hacer pruebas 3º probarlo con pip install -i https://testpypi.python.org faustilib

The other month a coworker of mine wanted to distribute a small wrapper he'd written for the Locu API. Instead of forcing developers to clone his repository, he wanted them to be able install with a single command: pip install locu. He wasn't sure how to go about this so I wrote up a quick guide, which I'm publishing below because I haven't found any other guides for this particular use case (python library hosted on github).

What is PyPI?

From the official website:

PyPI — the Python Package Index The Python Package Index is a repository of software for the Python programming language. Written something cool? Want others to be able to install it with easy_install or pip? Put your code on PyPI. It's a big list of python packages that you absolutely must submit your package to for it to be easily one-line installable.

Instructions

The good news is that submitting to PyPI is simple in theory: just sign up and upload your code, all for free. The bad news is that in practice it's a little bit more complicated than that. The other good news is that I've written this guide, and that if you're stuck, you can always refer to the official documentation.

I've written this guide with the following assumptions:

The module/library/package that you're submitting is called faustilib. faustilib is hosted on github. Create your accounts

On PyPI Live and also on PyPI Test. You must create an account in order to be able to upload your code. I recommend using the same email/password for both accounts, just to make your life easier when it comes time to push.

Create a .pypirc configuration file

This file holds your information for authenticating with PyPI.

[distutils] # this tells distutils what package indexes you can push to
index-servers =
    pypi # the live PyPI
    pypitest # test PyPI

[pypi] # authentication details for live PyPI
repository: https://pypi.python.org/pypi
username: fausti.informatica
password: i******0

[pypitest] # authentication details for test PyPI
repository: https://testpypi.python.org/pypi
username: iesfausti
password: i******0

This is just to make your life easier, so that when it comes time to upload you don't have to type/remember your username and password. Make sure to put this file in your home folder.

Prepare your package

Every package on PyPI needs to have a file called setup.py at the root of the directory. If your'e using a markdown-formatted read me file you'll also need a setup.cfg file. Also, you'll want a LICENSE.txt file describing what can be done with your code. So if I've been working on a library called faustilib, my directory structure would look like this:

root-dir/   # arbitrary working directory name
    setup.py
    setup.cfg
    LICENSE.txt
    README.md
    faustilib/
        __init__.py
        foo.py
        bar.py
        baz.py

Here's a breakdown of what goes in which file:

setup.py

This is metadata about your library.

from distutils.core import setup setup( name = 'faustilib', packages = ['faustilib'], # this must be the same as the name above version = '0.1', description = 'Una biblioteca de codigo del IES Fausti', author = 'Fausti Informatica', author_email = 'fausti.informatica@gmail.com', url = ' https://github.com/iesfausti/faustilib', # use the URL to the github repo download_url = ' https://github.com/iesfausti/faustilib/tarball/0.1', # I'll explain this in a second keywords = ['educacion', 'secundaria', 'fausti'], # arbitrary keywords classifiers = [], )

The download_url is a link to a hosted file with your repository's code. Github will host this for you, but only if you create a git tag. In your repository, type: git tag 0.1 -m "Adds a tag so that we can put this on PyPI.". Then, type git tag to show a list of tags — you should see 0.1 in the list. Type git push --tags origin master to update your code on Github with the latest tag information. Github creates tarballs for download at https://github.com/{username}/{module_name}/tarball/{tag}.

setup.cfg

This tells PyPI where your README file is. (No lo puedo crear bien!)

[metadata]
description-file = README.md

This is necessary if you're using a markdown readme file. At upload time, you may still get some errors about the lack of a readme — don't worry about it. If you don't have to use a markdown README file, I would recommend using reStructuredText (REST) instead.

LICENSE.txt

This file will contain whichver license you want your code to have. I tend to use the MIT license.

Upload your package to PyPI Test

Run:

python setup.py register -r pypitest This will attempt to register your package against PyPI's test server, just to make sure you've set up everything correctly.

Then, run:

python setup.py sdist upload -r pypitest You should get no errors, and should also now be able to see your library in the test PyPI repository.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages