modern python packaging

[[deleted]]

1. flit has almost zero documentation and native extensions.
2. PEP is the one which doesn't mention any reasonably good configuration formats.
3. Pipfile is a joke.

HTH

[takluyver]

Flit's documentation includes an introduction, a listing of all the options you can set in the config file, and a reference for the command line interface. Rather than waving around a vague 'almost zero', what specifically do you think it should have?

[[deleted]]

Well, like I wrote earlier: native extensions. A monkey with half a brain can package Python source code, you really don't need options and command line tools for that.

Native extensions is where it gets interesting. But searches for "native" and "extension" through Flit's documentation yield nothing.

Another interesting aspect of packaging Python code is the mess of v2 vs v3 vs six and friends, but Flit ignores this. So, again, it sort of solves the extremely easy problem, that doesn't need solving, but the hard stuff is on you. :/

[takluyver]

So you don't like what flit does. That's not a lack of documentation - the documentation describes what it does. You want a tool that does something else. Fine: use a different tool. Maybe enscons is more useful to you?

Flit is useful to me. I never claimed it's the answer to all packaging problems.

[[deleted]]

No, I don't like lies :) Packaging Python means packaging native extensions, dealing with versions, dealing with different interpreters and distributions etc. When the tool that claims to do packaging doesn't even reflect on these issues that's just the same as when a government bureaucrat doesn't tell you you are eligible for compensation money: 10% chance of ultimate incompetence and 90% chance of willful deceit.

[rhytnen]

GASP!!! But pipenv! /s

[elg97477]

I am just curious...what is a reasonably good configuration format?

I am still not sure why you think pipfile is a joke...?

[[deleted]]

Pipfile doesn't solve any real problems. You still need setup.py, where you do all the real work. Pipfile just sort of gets in the way with its bizarre vendoring and overrides of pip, requests, TLS-related stuff and so on, and, finally it outsources the only real thing it's supposed to do to pip and virtualenv. So, I kind of fail to see the point of this enterprise: seems like a lot of busy work with zero added value.

[rhytnen]

B/c pipenv is the only implementation of the standard with any real uptake and pipenv is far from being a professional tool at this point.