Python, fuuuuck youuuu and your stupid packaging system, and python devs who are bashing on js you douchebags ever tried NPM !!

delete your account

@broseph why though? maybe he has a point

@jesustricks delete my account

Are you using virtual environments? Node devs normally believe that every other packaging system will create sandboxes when it might not be necessarily the case. Languages like Python or Ruby would normally require isolated environments i.e conda/virtualenvwrapper for python rvm etc for ruby

@broseph will do, after you delete yours :D

Both are garbage but Python is slightly better than JavaScript 😉

@AleCx04 yes I'm using them but the point is that it's not as straightforward as npm or nvm

@12bitfloat Talking about packaging here, npm is much better in my opinion.

@milkyway really? In years of development i've yet to have an issue with either of the mentioned ones. What issues are you having?

@AleCx04 pick random 10 git repos in js and 10 in python (ex ai/ml repos), clone them and try running locally. How many issues will you run into in both sides

@milkyway what are the issues you often run into when doing so with python? not negating, just curious

@jesustricks mostly packages compatibility issues

@milkyway As a python dev: None? Only error sources packages still requiring Python 2 or depending on obscure not bundled C packages. Both is hardly PIPs but the package maintainers fault.
Of course by default dependencies are installed to the same location but it's just two lines to setup virtualenvs for them.

If you think Python packaging is bad now, you should have tried it seven years ago. Pip, distutils, setuptools, ez_install, pipenv, pyenv, poetry, blah blah. NPM might leave a little to be desired, but at least there are only two tools for JS.

pipenv was supposed to fix everything, but it has a bunch of annoyances (like, if you install a package that doesn't exist, it leaves it in the Pipfile to blow up every install until you remove it.

I tried NPM once. Can't remember which package I installed but when I saw it required nearly a thousand dependencies, I decided that I didn't actually want to use NPM any more.

@EmberQuill from one time you decided not to use it! at least it works

@milkyway none because I know what I am doing :D literally never had this issue and I have rather large codebases all over the place where I work(and have worked)

I did had issues way back when I was still learning/didn't know what I was doing. Didn't want to mention that since I didn't want to sound condescending.

check this for more https://medium.com/@alonisser/...

fuck you too

@vane Triggered? I'm not even calling names, but here you are proving my point.

@milkyway Well you tried and you failed. If you’re not prepared to do so about 1 million times more maybe it’s time to pick another career path since programming and failure are synonyms.

@vane lol, Who told you I gave up on it, The point is that npm is better than pip. it's simple. understand?

@milkyway yarn is better then npm, pip is better then npm just because like yarn it’s checking packages integrity.
Using npm is not secure, deal with that.

python -m pip install --force-reinstall pip-appreciation

@vane not even talking about yarn which belongs to js, and you can do “Security” and package integrity checks using npm.

Pip is horrible, but you can mitigate it using Virtualenv. NPM is horrible without ways to mitigate.