Hacker Newsnew | past | comments | ask | show | jobs | submit | eatox's commentslogin

On the contrary, it does see those imports, and indicates that those dependencies are used, but are not direct dependencies in your dependency tree, and instead installed because other dependencies rely on them: https://fpgmaas.github.io/deptry/rules-violations/#transitiv...


That's really useful. I find it really common for people to import transitive dependencies in python. A common one is putting something like matplotlib in deps then directly importing numpy. Seems to happen all the time.


Thank you for catching this! Indeed its not a bug.


It's sad to see so many negative comments here.

Quoting the GitHub page[0]:

> PDM is meant to be a next generation Python package management tool. It was originally built for personal use. If you feel you are going well with Pipenv or Poetry and don't want to introduce another package manager, just stick to it. But if you are missing something that is not present in those tools, you can probably find some goodness in pdm.

Having used PDM a bit, its ambition in my opinion may not be to replace existing tools, but rather to experiment and implement the most recent PEPs related to packaging.

While you can argue about PEP 582[1] implementation (which is still in draft), PDM doesn't prevent anyone from using virtual environments, and even provides a plugin[2] to support that. PDM also implements PEP 631[3], which most other package managers have been relunctant to support or slow to adopt.

[0]: https://github.com/pdm-project/pdm

[1]: https://www.python.org/dev/peps/pep-0582/

[2]: https://github.com/pdm-project/pdm-venv

[3]: https://www.python.org/dev/peps/pep-0631/


Thanks for the kind words on PDM. At time of creating PDM I don't want it to be similar with any other package mangers, so I chose PEP 582, and I thought I can play more new stuff on it.

But as PDM becomes mature, it is acknowleged by the Python packaging people, I also work hard to make PDM fit more people's workflow, fortunately, it has a strong plugin system. You can add virtualenv support(pdm-venv), publish command(pdm-publish) and more. In the future, I would like to see it can eventually push the iteration of PEP 582 and make it finalized.


Just made an account to say this. I am really impressed by your projects. I first found out about pdm after writing a small plugin for marko (which is amazing by the way) and checking out your github profile. I find what you write to be really well thought out and approachable.


God those PEP's are exactly what I need


This is understandable. But if it is experimental, please label is as such. No mention of that on the landing page right now.

EDIT: Oh, I should say: If it's meant to take over the world, say so, as well!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: