How to make a Python package in 2021 • Hacker News Board

Re: How to make a Python package in 2021

#11

Post by neolog » Thu, Apr 08, 2021, 2:59 AM UTC

zomglings wrote: post #8

The number of extra tools used in this article boggles my mind. Are you writing a simple library? Create a setup.py. Copy paste an existing setup.py and modify it to suit your purposes. Now you have a working, pip installable python package. Want to publish to PyPI? Use twine. It's standard and it's simple. You don't need complicated tooling for simple projects.

How do you handle version pinning? hash checking? CI? testing on multiple platforms? multiple python versions? deployment? credential management? package data? version bumps?

Sure, experts know how to do all these things because they spent many days learning them, but I'd rather outsource to a tool.

Re: How to make a Python package in 2021

#12

Post by [deleted] » Thu, Apr 08, 2021, 2:59 AM UTC

someoldguy wrote: post #9

zomglings wrote: post #8

The number of extra tools used in this article boggles my mind. Are you writing a simple library? Create a setup.py. Copy paste an existing setup.py and modify it to suit your purposes. Now you have a working, pip installable python package. Want to publish to PyPI? Use twine. It's standard and it's simple. You don't need complicated tooling for simple projects.

I would probably recommend just following https://packaging.python.org/tutorials/packaging-projects/ instead.

[deleted]

Re: How to make a Python package in 2021

#13

Post by brandmeyer » Thu, Apr 08, 2021, 3:05 AM UTC

Lets see how many high-quality Python packaging guides we can cram into one discussion, shall we?

I have no problems using setuptools directly, as outlined in https://packaging.python.org/guides/distributing-packages-us...

Re: How to make a Python package in 2021

#14

Post by perrygeo » Thu, Apr 08, 2021, 3:07 AM UTC

Why not to make a Python package in 2021.

Even as a long time Python user, the packaging ecosystem feels fragmented and error-prone at best. Honestly, it sours the experience of writing Python code knowing you might eventually need to make it work on another computer.

Re: How to make a Python package in 2021

#15

Post by zomglings » Thu, Apr 08, 2021, 3:07 AM UTC

neolog wrote: post #11

zomglings wrote: post #8

The number of extra tools used in this article boggles my mind. Are you writing a simple library? Create a setup.py. Copy paste an existing setup.py and modify it to suit your purposes. Now you have a working, pip installable python package. Want to publish to PyPI? Use twine. It's standard and it's simple. You don't need complicated tooling for simple projects.

How do you handle version pinning? hash checking? CI? testing on multiple platforms? multiple python versions? deployment? credential management? package data? version bumps? Sure, experts know how to do all these things because they spent many days learning them, but I'd rather outsource to a tool.

Iteratively. You don't need to solve all those problems at once.

Version pinning can be done in setup.py using the same syntax you would see in a requirements.txt file. You should be very conservative when pinning versions in a library, though.

You can lean on your ci tool (eg. Github actions) to handle testing, hash checking, credential management, etc. But I recommend all of this start as a bunch of locally runnable scripts.

I typically bump version directly in a version file and move on with my life.

This stuff usually builds up iteratively and at least for me has never been the starting point. Starting point should be a library worth sharing. It is not the end of the world of you release the first few versions manually.

Re: How to make a Python package in 2021

#16

Post by zomglings » Thu, Apr 08, 2021, 3:08 AM UTC

someoldguy wrote: post #9

zomglings wrote: post #8

The number of extra tools used in this article boggles my mind. Are you writing a simple library? Create a setup.py. Copy paste an existing setup.py and modify it to suit your purposes. Now you have a working, pip installable python package. Want to publish to PyPI? Use twine. It's standard and it's simple. You don't need complicated tooling for simple projects.

I would probably recommend just following https://packaging.python.org/tutorials/packaging-projects/ instead.

Ah I'm stuck in the dark ages.

Re: How to make a Python package in 2021

#17

Post by modi123 » Thu, Apr 08, 2021, 3:10 AM UTC

Test

Re: How to make a Python package in 2021

#18

Post by da39a3ee » Thu, Apr 08, 2021, 3:13 AM UTC

zomglings wrote: post #8

The number of extra tools used in this article boggles my mind. Are you writing a simple library? Create a setup.py. Copy paste an existing setup.py and modify it to suit your purposes. Now you have a working, pip installable python package. Want to publish to PyPI? Use twine. It's standard and it's simple. You don't need complicated tooling for simple projects.

You seem to have missed the point. The project in the article was simple because that is best for exposition. The article would hardly have been more helpful with the code for a realistic python package dumped into it, would it?

Re: How to make a Python package in 2021

#19

Post by void_mint » Thu, Apr 08, 2021, 3:15 AM UTC

neolog wrote: post #3

Just use Poetry [1]. It's popular and works well. [1] https://python-poetry.org/

Holy crap, for some reason I never thought to consider another package manager than Pip, which I loathe.

Re: How to make a Python package in 2021

#20

Post by sergiomattei » Thu, Apr 08, 2021, 3:16 AM UTC

neolog wrote: post #3

Just use Poetry [1]. It's popular and works well. [1] https://python-poetry.org/

Huge thumbs up to Poetry. It's drastically simplified package management for me and replaced Pipenv (which I simply dreaded working with due to performance and DX issues).

I no longer start Python projects without Poetry. It's really good.

EDIT: Also, it's being integrated to most PaaS as well. I deploy to Render.com with Poetry now.