3 ms·
I saw the first of the posts he mentions, and yes, I was very surprised to see the negativity. There is literally no reason to be negative, if you don't like th
by StavrosK 9y ago
I saw the first of the posts he mentions, and yes, I was very surprised to see the negativity. There is literally no reason to be negative, if you don't like the tool, use another. People seem to be upset that Pipenv is the recommendation now, but it's better than pip, and it should be the recommendation until something better comes along.
I'm more upset about the whole pyproject.toml thing that means I have to migrate everything again, from Pipfile this time, even though I have barely finished migrating to it!
- jsmeaton 9y agoI believe they have different use cases. Pyproject.toml is more akin to setup.py (and publishing libraries) where Pipfile is to replace requirements (and building apps). All the people arguing over the “blessedness” seem to be ignoring this.
- StavrosK 9y agoI think pyproject.toml is meant to be a superset, which means it would replace the Pipfile as well as all the other files. It's a welcome change, but I hate that we went through the short-lived Pipfile intermediate step.
- adventured 9y agoI used to buy into the premise that anonymity + Internet = lots of people acting badly. Social media over the last decade has taught me that anonymity is absolutely not a meaningful requirement (I believe the masses of users, over that time, have adjusted to being comfortable with publicly being jerks without much concern). A lot of people feel no need to have a good reason to be jerks, it's their character, it's who they are all the way down. Some people are just rotten and there isn't much more than that to it (as it pertains to dealing with them as shit throwing types on the Internet). I feel like the author is suffering from not understanding or not accepting that this is the case, that in many or most instances, a person doesn't have a good reason for their terrible behavior online. The reason for the clichéd build you up, tear you down, repetition process throughout all of human history, is that a vast number of people will be rage monsters, petty, filled with envy and jealousy. The types that are prone to that ill behavior, will come pouring out of the woodword once you've acquired any consequential amount of success/money/fame/whatnot. These are not good people, they are not capable of reasoned discourse, their opinions do not matter, their hostile negativity should be ignored and disregarded accordingly (they're also, fortunately, extraordinarily easy to spot and separate out from the more reasoned criticism; their entirely unnecessary over-the-top negative behavior provides for easy filtering).
- ubernostrum 9y agopyproject.toml isn't another way to specify dependencies for Python code. The long version of why it exists: Historically, a Python package has been defined by the existence of the setup.py file. Executing this file with various command-line arguments is how packaging tasks are carried out: 'setup.py install' installs the package, 'setup.py sdist' builds a source distribution (.tar.gz) suitable for uploading to a package repository, etc., etc. But this workflow has dependencies! Most packages will only depend on setuptools (which supplies the setup() function) and wheel (which supports building binary packages), so the packaging tooling assumes the presence of setuptools and wheel and you never have to specify them as explicit dependencies (in the old old days, setuptools used a drive-by installer file bundled into the package so people who didn't have setuptools could still install setuptools-based packages; nowadays, pip supplies it automatically). But what if you have a workflow that requires something else? What if you use an alternative package manager, or package build tool, or really anything that isn't setuptools or wheel? How do you specify the toolchain you need to work with your package? That is the thing pyproject.toml solves. Since it's not an executable Python file, it can't get stuck in a chicken-and-egg problem ("execute setup.py to find out what you need to execute setup.py"), and it can specify the necessary build system for a package in a standardized way.
- StavrosK 9y agoYes, I understand the purpose, but the result is that it replaces any previous way of specifying dependencies. It's great that it exists, but it's frustrating that it was developed right when the new thing for specifying dependencies (Pipfile) was starting to become popular.
- ubernostrum 9y agoIf you think it's another "thing for specifying dependencies" in the category of the pipenv Pipfile, you have not understood the purpose of pyproject.toml.
- StavrosK 8y agoIf you think that's what I think, you haven't understood my comment. Again, I'm saying that I don't want to migrate to yet another format so soon, even if it does much more than just specify dependencies.