News for hackers. Stuff that matters.
Re:Learning Go as a Python Developer: The Good and the Bad by takeda on Monday July 18, 2022 @07:47PM (#32145629)
But Python has a decent and a reproducible way of installing packages. The problem python has is that things evolved over time, so you can find on the net plenty of outdated information. There is also a lot of blogs and articles with bad practices, most written by people that got something working.

I think also a lot of issues with packaging is ironically because of PyPA that supposed to work on a standard, but in reality instead of embracing and promoting something that works they just pushes half-assed solutions because author is one of the members. Kind of like they were pushing failed Pipenv "for humans". Seems like Poetry is generally popular and devs are happy with it, so of course PyPA started pushing their own Hatch project, because python packaging was finally getting too straight forward.

I think Python would benefit as a whole if PyPA was just dissolved.

Re:Learning Go as a Python Developer: The Good and the Bad by oarabbus_ on Monday July 18, 2022 @09:10PM (#32146232)
>But Python has a decent and a reproducible way of installing packages.

Reading the comment thread it's not immediately clear what the answer is - it seems implied that the proper way is using Poetry, is that the case?

Re:Learning Go as a Python Developer: The Good and the Bad by stavros on Tuesday July 19, 2022 @04:43AM (#32149016)
To me, yes. Poetry for me has been fairly straightforward, in anything I needed to do (dependency management, package publishing, etc).
Re:Learning Go as a Python Developer: The Good and the Bad by blooalien on Wednesday July 27, 2022 @09:16AM (#32250028)
Poetry has been the one I've settled on as well. It "Just Works™" for everything I've used it for thus far, and it's even been easy to convert older methods I've tried to the Poetry way of doing things.
Re:Learning Go as a Python Developer: The Good and the Bad by Ygg2 on Tuesday July 19, 2022 @12:40AM (#32147612)
It's not.

See https://imgs.xkcd.com/comics/python_environment_2x.png

Or sometime the computer is haunted and my colleague had problems installing tensorflow. To this day he has no working tensorflow.

Re:Learning Go as a Python Developer: The Good and the Bad by takeda on Wednesday July 20, 2022 @01:35AM (#32161827)
I suppose we can follow memes or facts.

Please note I never used tensorflow on that computer in fact I never used tensorflow, but this is my experience: https://gist.github.com/takeda/89ec29501b6e8641415668f22f3e9...

It succeeded after first try.

I do see that in their repo[1] they use a non standard way to build the package. They use Bazel, but that's Google for you. They never do things everyone else is doing. I'm not sure why this is Python problem rather than package problem.

They have tons of open issues around building: [2]

[1] https://github.com/tensorflow/tensorflow

[2] https://github.com/tensorflow/tensorflow/labels/type%3Abuild...

Re:Learning Go as a Python Developer: The Good and the Bad by Ygg2 on Wednesday July 20, 2022 @03:27AM (#32162611)
That's the thing. It's not a meme. It's a joke, that rings true.

It works fine for me.

Not for him. Same package, nearly identical laptops, different outcomes.

And I as newcomer to Python, there are like four (pip, venv, brew, conda) cli APIs that I had to learn just to get working on some Python file.

Re:Learning Go as a Python Developer: The Good and the Bad by leetrout on Monday July 18, 2022 @08:57PM (#32146122)
> I think Python would benefit as a whole if PyPA was just dissolved

STRONG agree. And I hate the cult of personality that was previously (still?) strong.

Re:Learning Go as a Python Developer: The Good and the Bad by akagusu on Monday July 18, 2022 @10:37PM (#32146898)
I think we can get a good package management system for Python if we get rid of PyPA.