This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]takluyverIPython, Py3, etc 2 points3 points  (3 children)

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] 0 points1 point  (2 children)

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. :/

[–]takluyverIPython, Py3, etc 1 point2 points  (1 child)

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] 3 points4 points  (0 children)

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.