What the Heck Is Pyproject.toml?

Re:What the Heck Is Pyproject.toml? by jshen on Thursday April 02, 2020 @05:56PM (#22764321)

It’s really not the same. Gemfile lists the direct dependencies of your project with variable specificity of explicit versions. Gemfile.lock lists all dependencies after resolving your direct dependencies and locks them to specific versions. requirements.txt is some bastardization of both of these combined, and setup.py is neither of these it’s for distribution of modules/packages which Ruby has as well, but it’s not your gemfile.

edit: also, how do you manage dev dependencies with requirements.txt and setup.py?

[ Parent | on HN ]

Re:What the Heck Is Pyproject.toml? by viraptor on Thursday April 02, 2020 @06:07PM (#22764397)

You can put dev deps in extras in their own "dev" block. Similar to how gemfile uses groups. Use requirements-dev.txt for them. Requirements for is a full list of dependencies after resolution and their exact versions. (as produced by freeze) The main difference is that requirements is "as installed in current configuration", while gemfile.lock is "for any groups configuration".

Again, not as polished experience, but the model matches.

[ Parent | on HN ]

Re:What the Heck Is Pyproject.toml? by jshen on Thursday April 02, 2020 @10:08PM (#22765775)

But it’s all ad hoc which is problematic. You’re solving it yourself, the tool isn’t solving it. It’s like saying that C is the same as python, you can just write your own garbage collector in C!

[ Parent | on HN ]