Search for a command to run...
I’m the founder and CEO of Okteto, where we’re busy re-imagining the developer experience for cloud native applications.
Before Okteto, I built enterprise chat products at Atlassian, application lifecycle management tools at Elasticbox (now part of Centurylink) and cloud services at Microsoft Azure.
No comments yet. Be the first to comment.
https://www.youtube.com/watch?v=tcgQyrkS7Qs he bottleneck for AI in software development isn't smarter models. It's giving agents a real place to run. Back on The Software Plaza with Twain Taylor f
Platform Engineering Day North America 2026
KCD San Francisco Bay Area 2025
Earlier today, I had the privilege of speaking with a group of young entrepreneurs through the 3percentclub , an organization dedicated to increasing diversity in tech by providing underrepresented talent with accessible education. My friend Maria As...
Platform Engineering Day Europe 2025
Once you have a module that can be pip installed from git, the next logical step is to make it available directly from pypi. Doing this will allow your users to install your module locally by simply calling: pip install your-module , instead of having to deal with git repository access and addresses.
The first thing to do is to create a pypi account. All you need is an email, and to pick a username and a password. I also recommend you to create an account on pypi's test server, so we can validate our module before pushing to production.
We're going to create a settings file for our pypi credentials, so we don't have to type the urls and usernames again and again. Create a ~/.pypirc file like this one (replace my username with yours):
[distutils]
index-servers =
pypi
test
[pypi]
repository = https://pypi.python.org/pypi
username = MY_USERNAME
password = MY_PASSWORD
[test]
repository = https://testpypi.python.org/pypi
username = MY_USERNAME
password = MY_PASSWORD
I chose to set have the password there for simplicity. If you don't think this is secure enough, you can remove the password lines and instead provide them manually everytime you run the upload commands
In order to generate a source distribution, we need a version. Edit your setup.py file, and update the version of it to match the version you want to create. Remember that it needs to match the public version identifier scheme.
On your terminal, go to the root of your module, and create the distribution. I recommend you to use source distributions, unless you really know what you're doing and think that wheels is better:
python setup.py sdist
If the command ran successfully, a dist folder will be created, with the source distribution file inside. It's the one named YOUR_MODULE-YOUR_VERSION.tar.gz.
Once you have a source distribution file, it's time to upload it. Fist, you need to register your module in pypi, by filling up this form. Do the same in the test serv
twine upload --repository test dist/YOUR_MODULE-YOUR_VERSION.tar.gz
Once the file is upload, install it locally at least once, to make sure everything works as expected:
virtualenv pip_test --clear
source pip_test/bin/activate
pip install -i https://testpypi.python.org/pypi YOUR_MODULE==YOUR_VERSION
If everything works fine, you will have a virtual environment with your module. I recommend you double check the version installed and run some tests, just to be sure.
Finally, we push to pypi:
twine upload --repository test dist/YOUR_MODULE-YOUR_VERSION.tar.gz
If the upload finished successfully, your module will the available to the world in the next 2-3 minutes.
Hope it helps!