3 ms·
I think this article is rather long-winded and not super informative. The previous post [1] lays out what one should actually do, and I agree with most of it,
by linuxftw 3y ago
I think this article is rather long-winded and not super informative. The previous post [1] lays out what one should actually do, and I agree with most of it, at least from a developer perspective.
1: https://www.bitecode.dev/p/relieving-your-python-packaging-pain https://www.bitecode.dev/p/relieving-your-python-packaging-p...
- BiteCode_dev 3y agoThis post is the justification of the one you link to. It's not meant to be practical, but rather an answer to the same comments I get over and over again when I suggest the method you just posted. Even with it though, you can see in the thread people don't read it and completely ignore its rational :)
- linuxftw 3y agoI understand what you're trying to achieve here, but I think the content isn't very well organized. The people that have the chops to understand most of what you wrote won't need to read it, and those that don't won't come away with any clearer understanding. If you can trim the content to about 30% length, I think it would be better.
- BiteCode_dev 3y agoYes, it's too long, I should have made a series of 3 posts instead, each focused on one particular idea. One particular point "devs lie", really deserve its own article. Because we do lie a lot, and it's like a taboo to talk about it.
- linuxftw 3y agoI don't think I'd characterize some of those things as lying. Setting up a development environment is no different than setting up other kinds of software: you obtain the software, and follow instructions to get it up and running. There's no substitute for this, unless you're setting up an environment for someone else (eg, a student), in which case, they don't need to know about many of the details.