Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

If this project is dead, just tell us

github.com

Post reply on HN
Print view View original

71–80 of 325 posts

Re: If this project is dead, just tell us

#71

Post by rpedela »

madeofpalk wrote: post #53
josteink wrote: post #24

Earlier quoted context omitted.

> Python packaging in general is such a messy ecosystem Not just messy. It’s probably worst in class. I at least can’t come up with a single worse package-management story which I do know of. Edit: I’m talking about platforms with actual package-management which sucks, not platforms with the absence of package-management all together.

I thought NPM was everyone's favourite hated package manager/repository?

It is, at least on HN, but it is also one of the best overall.

Re: If this project is dead, just tell us

#72

Post by Noe2097 »

ScoutOrgo wrote: post #38

Serious question, what does pipenv (and poetry) have over conda?

Conda works with a different, parallel ecosystem, whose main source of packages is managed by a single company (Anaconda Inc). That company validates, rebuilds, and possibly silently patches code, to provide their own packages.

pipenv brings simpler workflow to pip. pip leverages packages which are published by their authors onto pypi, which is managed by the Python Foundation.

Re: If this project is dead, just tell us

#73

Post by casion »

guardian5x wrote: post #33
casion wrote: post #18

669 commits in the last year... and asking if the project is dead? I'm a bit confused here. Maybe the project is mismanaged, or there's some upstream issue with package distro, but it seems to be far from dead.

He talks about maintenance and making releases. Otherwise people will still deal with bugs in the "current" release that have been fixed in the master branch for a long time.

That would be mismanagement (and annoying of course), not "dead" I would think?

Re: If this project is dead, just tell us

#74

Post by klyrs »

de_watcher wrote: post #34
valdiorn wrote: post #9

This is all MIT licensed, if people care so much, why has nobody forked this? Why are people talking about jumping ship to a completely different project instead of forking and cutting a new release from there?

Title and comments in that issue thread show that people misunderstand how the FOSS works. Maintainer is not 'the project', it's the current direction that shapes incoming pull requests.

This viewpoint doesn't account for authenticity as verified by, e.g., PyPi. Yes, you can use anybody's pipenv, but most people would greatly prefer to not go to such lengths.

Re: If this project is dead, just tell us

#76

Post by dragonwriter »

css wrote: post #3

Why would someone choose to use a third party library when the first party solution[0] is more than adequate in the first place? [0] https://docs.python.org/3/library/venv.html

Isn't pipenv a dependency management system that includes the python distribution by way of managing a venv, rather than a simple replacement for venv, sort of like poetry (though poetry, I think, does a better job, but for the problem that it doesn't seem to respect SSL options available for pip which are often needed in enterprise environments)?

Re: If this project is dead, just tell us

#77

Post by fock »

mikkelam wrote: post #8

Pipenv has spawned so much controvery.. One big shitfest. Python packaging in general is such a messy ecosystem

maybe for web-development and ML. For my core scientific workflows I have about, uuuh, 10(?) libraries. And those are generally stable enough to upgrade 1 without breaking the other. Seems like the problem is with the users.

Re: If this project is dead, just tell us

#78

Post by xenator »

ScoutOrgo wrote: post #38

Serious question, what does pipenv (and poetry) have over conda?

Very different ecosystems. Its like recipe of pancakes on vegan and normal sites. It is doing the same but different target audience. For example, I rarely saw instruction for packages how to install it for conda except for cases when it is DS/ML oriented.

Re: If this project is dead, just tell us

#79

Post by mateuszf »

theamk wrote: post #48
josteink wrote: post #24

Earlier quoted context omitted.

> Python packaging in general is such a messy ecosystem Not just messy. It’s probably worst in class. I at least can’t come up with a single worse package-management story which I do know of. Edit: I’m talking about platforms with actual package-management which sucks, not platforms with the absence of package-management all together.

Cmake? (And especially Kitware Superbuild... try pinning packages there!)

Isn't it a build tool, not package manager?

Re: If this project is dead, just tell us

#80

Post by akvadrako »

Scarblac wrote: post #69
guggle wrote: post #56

Earlier quoted context omitted.

I don't get it either... nor do I understand why venv is considered difficult to use. "It automatically creates and manages a virtualenv for your projects, as well as adds/removes packages from your Pipfile as you install/uninstall packages." Well, thanks but automate "python -m venv myvenv" ? Add/remove packages from a "Pipfile" ? Do I have to specify dependencies somwhere else than requirements.txt ? Why ? There mu…

It's about dependencies of dependencies. Requirements.txt only lists versions of your project's requirements, but Pip actually automatically installs dependencies of those requirements too. And those versions aren't listed in your requirements.txt. https://realpython.com/pipenv-guide/#dependency-management-w... -- This page about Pipenv vs pip + virtualenv goes into more detail.

It’s easy to also get the versions of all sub dependencies and put them in requirements.txt
Post reply on HN