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

Ask HN: Is anyone using PyPy for real work?

news.ycombinator.com

Post reply on HN
Print view View original

101–110 of 185 posts

Re: Ask HN: Is anyone using PyPy for real work?

#101

Post by sanderjd »

rlpb wrote: post #64
smashed wrote: post #49

Earlier quoted context omitted.

You're not really answering why they are important? Is it because .deb packages will install inside dist-packages and when you run pip install as root without a virtual env, it installs inside site-packages? I don't really see how this helps though? Sure you won't get paths to clash between the two but you still have duplicate packages which is probably not what you want..

Debian ships packages with a coherent dependency structure that crosses language boundaries. You don't need to care what language something is written in to be able to "apt install" it. The expectation is that if it "apt installed" then it should Just Work because all the required dependencies were also pulled in from Debian at the same time. Debian also tries to ship just one version of everything in a single distri…

Yep, I screw things up all the time with packages in homebrew that are written in python, when I forget to switch into a virtual env before doing stuff with pip. Debian's solution seems very sensible. And it is the same solution as homebrew, I suppose, as long as you don't interact with any of the homebrew-installed packages via pip. But I find it quite easy to accidentally do that.

Re: Ask HN: Is anyone using PyPy for real work?

#102

Post by Qem »

I can't really use it at work, due to restrictive corporative policy in place. I don't control my workstation setup, and I'm only allowed vanilla CPython there. Regarding this, I wished PyPy were pip installable from inside CPython, like Hylang and Pyston do.

But while programming as a hobby at home, mostly small-scale simulations, PyPy is my default interpreter for Python. It seems PyPy has a sweet spot on code written relying heavily on OOP style, with a lot of method calls and self invocation. I consistently get 8-10x speed improvements.

Re: Ask HN: Is anyone using PyPy for real work?

#103

Post by saila »

eigenvalue wrote: post #91

Thanks for reminding me to look at PyPy again. I usually start all my new Python projects with this block of commands that I keep handy: Create venv and activate it and install packages: python3 -m venv venv source venv/bin/activate python3 -m pip install --upgrade pip python3 -m pip install wheel pip install -r requirements.txt I wanted a similar one-liner that I could use on a fresh Ubuntu machine so I can try out…

For a more apples to apples comparison, you would install pypy using your package manager, e.g. apt install pypy3 or brew install pypy3. On Linux, you might have to add a package repo first.

Re: Ask HN: Is anyone using PyPy for real work?

#104

Post by nicce »

eigenvalue wrote: post #91

Thanks for reminding me to look at PyPy again. I usually start all my new Python projects with this block of commands that I keep handy: Create venv and activate it and install packages: python3 -m venv venv source venv/bin/activate python3 -m pip install --upgrade pip python3 -m pip install wheel pip install -r requirements.txt I wanted a similar one-liner that I could use on a fresh Ubuntu machine so I can try out…

Just a note; these scrips are not comparable in monstrosity as the first is about to initiate the project when as the second one is to initiate whole PyPy installation.

So if you have PyPy already on your machines;

  pypy -m venv venv && \
    source venv/bin/activate && \
    pip install --upgrade pip && \
    pip install wheel && \
    pip install -r requirements.txt
Was not that bad after all, when my initial thought was that do I need all the above to just initiate the project :D

Re: Ask HN: Is anyone using PyPy for real work?

#105

Post by tech2 »

sanderjd wrote: post #101
rlpb wrote: post #64

Earlier quoted context omitted.

Debian ships packages with a coherent dependency structure that crosses language boundaries. You don't need to care what language something is written in to be able to "apt install" it. The expectation is that if it "apt installed" then it should Just Work because all the required dependencies were also pulled in from Debian at the same time. Debian also tries to ship just one version of everything in a single distri…

Yep, I screw things up all the time with packages in homebrew that are written in python, when I forget to switch into a virtual env before doing stuff with pip. Debian's solution seems very sensible. And it is the same solution as homebrew, I suppose, as long as you don't interact with any of the homebrew-installed packages via pip. But I find it quite easy to accidentally do that.

  export PIP_REQUIRE_VIRTUALENV=1
has been quite helpful in the past as pip then refuses to just install things directly.

Re: Ask HN: Is anyone using PyPy for real work?

#107

Post by eigenvalue »

nicce wrote: post #104
eigenvalue wrote: post #91

Thanks for reminding me to look at PyPy again. I usually start all my new Python projects with this block of commands that I keep handy: Create venv and activate it and install packages: python3 -m venv venv source venv/bin/activate python3 -m pip install --upgrade pip python3 -m pip install wheel pip install -r requirements.txt I wanted a similar one-liner that I could use on a fresh Ubuntu machine so I can try out…

Just a note; these scrips are not comparable in monstrosity as the first is about to initiate the project when as the second one is to initiate whole PyPy installation. So if you have PyPy already on your machines; pypy -m venv venv && \ source venv/bin/activate && \ pip install --upgrade pip && \ pip install wheel && \ pip install -r requirements.txt Was not that bad after all, when my initial thought was that do I…

That's true, but you can run the first block of commands on a brand new Ubuntu installation because regular CPython is installed by default. Whereas you would need to do the whole second block when starting on a fresh machine.

Re: Ask HN: Is anyone using PyPy for real work?

#108

Post by comboy »

A bit meta. It seems like it would be nice to have no-action tickets for open source projects.

Quite often you would want to just thank somebody, or say that you would prefer it that way and don't understand why is it this way or it would be cool to have this or that, but of course opening ticket on github feels like wasting time of the maintainer and especially when you have some feedback like e.g. what would you like to see or what you do and don't like it feels entitled because well you can do it yourself, you can fork etc.

It would need to be low friction for both sides. Preferably with no way to respond so that there's zero pressure and little time waste for maintainers.

Mail feels like you want something, it works for thank you but still feels bad on receiving end when you just ignore them.

Re: Ask HN: Is anyone using PyPy for real work?

#110

Post by eigenvalue »

saila wrote: post #103
eigenvalue wrote: post #91

Thanks for reminding me to look at PyPy again. I usually start all my new Python projects with this block of commands that I keep handy: Create venv and activate it and install packages: python3 -m venv venv source venv/bin/activate python3 -m pip install --upgrade pip python3 -m pip install wheel pip install -r requirements.txt I wanted a similar one-liner that I could use on a fresh Ubuntu machine so I can try out…

For a more apples to apples comparison, you would install pypy using your package manager, e.g. apt install pypy3 or brew install pypy3 . On Linux, you might have to add a package repo first.

I find that much scarier to do personally since it seems a lot more likely to screw up other stuff on your machine, whereas with pyenv it's all self-contained in the venv. Also using apt packages tends to install a pretty old version.
Post reply on HN