python 3.4 please ;_;
The problem, which they keep mentioning over and over, is that companies who actually donate have zero interest in a python 3 version. While they are a non profit, they have to pay the bills somehow.
PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
71–80 of 150 posts
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#72According to data I'm getting a 20X performance increase from the rendering engine in Django. I know this is the least of the time I spend but it's significant enough to take a deeper look.
You may be surprised, I've seen a lot of Django setups where template rendering was the slowest or second-slowest part of their system behind DB queries.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#73Earlier quoted context omitted.
Personally I'd be quite excited to see a bug I reported fixed the same-day - of course people's expectations are different it's not always easy to balance these things.
One of the rewards of participating in OSS is to make your name visible, this can then be used as creds to gain commit rights or to talk at conferences as well as proof of competence when looking for a job. Interestingly, I've had the same experience when reporting and asking how to contribute to Python 3, not by a core dev but somebody "stealing" my bug and quickly submitting a patch!
Something similar happened that left me with mixed feelings recently. I recently came up with a new feature idea for Python, and a core dev ran with it. I was very happy at first, but then he wrote a pep, implemented it, and got all the congrats.
I had hoped to help, and put something on my resume, but was shut out. "Thanks for improving my pep" on a mailing list is all the credit I got (and work I was able to do on it). Kind of disappointing, though I will enjoy the feature.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#74Kudos to the pypy team! I suspect pypy would benefit from some kind of marketing campaign. It rarely lets me down and yet lots of python devs don't know about it. The most popular package(s) that don't work with it have been numpy, scipy, etc. When I first encountered pypy, there was a numpypy and I wouldn't be surprised if that's different now. But bottom line, tons of python code out there needs more performance an…
Is PyPy going to support Python 3? We kind of need the ecosystem to move forward, and Python 3 has a lot of niceties...
Doesn't it already? 3.2.5 it seems.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#75python 3.4 please ;_;
The problem, which they keep mentioning over and over, is that companies who actually donate have zero interest in a python 3 version. While they are a non profit, they have to pay the bills somehow.
Chicken and egg... But if there was good Python 3 support maybe more companies would contribute.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#76> We would also like to thank our contributors (7 new ones since PyPy 2.6.0) and encourage new people to join the project. PyPy has many layers and we need help with all of them This doesn't match my experience of the PyPy project. I found a tiny bug in the stdlib matching against CPython, went into IRC to ask a question about test running to be sure I got it right and was quickly engaged in conversation about why I…
On the flip side of this thread, some projects have started to adopt specific tagging in their issue systems for folks looking to get started as contributors. I really like this as it's clear communication to both new contributors and to existing contributors that the issue in question is an on-ramp for the project. Here's Neovim's "entry-level" label, for example: https://github.com/neovim/neovim/issues?q=is%3Aopen+…
Actually pypy tries to do the same, bitbucket does not support tagging very well though (but looking for "easy" or something in the issue tracker helps). I am personally sorry if the poster had an experience like that, IRC is difficult to communicate over, it must have been a misunderstanding
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#77> We would also like to thank our contributors (7 new ones since PyPy 2.6.0) and encourage new people to join the project. PyPy has many layers and we need help with all of them This doesn't match my experience of the PyPy project. I found a tiny bug in the stdlib matching against CPython, went into IRC to ask a question about test running to be sure I got it right and was quickly engaged in conversation about why I…
This is very very disingenuous.
Here are the public IRC logs for what I assume you're referring to (which is from July 2014 by the way):
https://botbot.me/freenode/pypy/2014-07-02/?msg=17362202&pag...
You found a bug in an old version of PyPy. A core developer told you you might want to try a new one. No one stole your shot out from under you.
You would undoubtedly be welcomed to contribute. Don't post FUD.
Disclaimer: I am not a PyPy core dev but I do work closely with them.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#78> We would also like to thank our contributors (7 new ones since PyPy 2.6.0) and encourage new people to join the project. PyPy has many layers and we need help with all of them This doesn't match my experience of the PyPy project. I found a tiny bug in the stdlib matching against CPython, went into IRC to ask a question about test running to be sure I got it right and was quickly engaged in conversation about why I…
Not everyone can get it right all the time.
Fixed a bug the same day someone asked about it and some potential contribute blame you for not letting them fix entry level bug.
Answering people with "patch welcome" and people blame you for not fixing it.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#79The good news never stops with these guys. PyPy is so good that I've stopped considering myself a "Python programmer" to a "PyPy programmer" over the last few years.
Best of every world. I get my preferred language and eliminate CPU performance worries.
For me, targeting development on PyPy has taken the place of migrating to Python3. Which just moves too fast in effort to pull people over, Python is too big for that strategy. At this point, people want speed with a great language, they want PyPy! The PyPy team has pretty much enabled the perfect development stack. I use PyPy+Django+gunicorn+Nginx and no problems.
Keep up the great work.
Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More
#80python 3.4 please ;_;
Yes, this is one of those features that should be targeting the newest release, to provide a reason to upgrade, and not support lock-in to 2.7.