Live data from Hacker News

PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

morepypy.blogspot.com

51–60 of 150 posts

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#51
post #47
post #23

Earlier quoted context omitted.

Working on it (even wrote 2 blog posts recently about it). Mercurial is an interesting benchmark/use case for us.

Yay! Glad to hear it. Using Python makes me so envious of Perl's startup time. Maybe some day we can have that in Python too... Where are those blog posts?

[deleted]

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#52

Earlier quoted context omitted.

I can understand that, I certainly would have been stoked about a bug report being fixed on the same day; I hadn't reported the bug though. I was working on providing a bug report with a patch alongside it and (perhaps foolishly) mentioned the bug informally as context as to why I was doing this.

Without being privy to the entire context, what I think might've happened is that your discussion caught the interest of a core developer who then picked it up and ran with it. I doubt they intended to step on your toes as a consequence of fixing the problem. Hackers tend to be intrigued by problems, including small ones, and especially ones that cause software behavior to deviate from expectations. The other side of…

I'm a long-term FLOSS contributor, but I've also served on the boards of 501(c)(3)s, I've been a mentor for Google Summer of Code for most of the times the programme has run and I've run workshops at my local university about getting involved in open source. I know what is involved in making a community welcoming to new contributors. If a project is putting an explicit call for contributions in updates that implies they're not getting as many as they'd like, which fits my experiences.

What you say about hackers getting nerd-sniped is true, but "that's just how coders are" certainly isn't. If you're a core developer for a project and you want the community to grow rather than diminish it's your responsibility to make it socially welcoming as well as having a low technical barrier to entry. I personally have spent many hours responding to emails about problems I could have fixed trivially, but if I'd done that the potential new contributor may not have grown into someone that's regularly fixing bugs I can't fix trivially. I'm not taking the unwelcoming attitude personally, I'm acting accordingly. If I can't get the information from a community I need to participate but I can get them to do the work by just throwing it over the fence I'd be crazy to continue to try and help them unless I have a very strong reason to outside of requiring fixes.

As to your point about reading minds, this is specifically mentioned in my initial comment. I asked about a problem running tests, and when I provided the context that I was asked for (I'm trying to put together a patch for this bug) there should have been no question as to motivation.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#54
post #7

python 3.4 please ;_;

The value of PyPy is that it is a thing you can just drop in to make your code faster. If PyPy wants to gain any traction they pretty much have to concentrate on the version with the most existing code.

Python 3 is the future. There's a chance that when Pypy finally catches up with Python 2.7 (numpy, C extensions etc), it will be obsolete.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#55
post #41
post #8

Earlier quoted context omitted.

> But bottom line, tons of python code out there needs more performance and has no dependency on numpy or any C extensions. What they need is nice JIT engines like PyPy and not to switch languages. If no one invested in improving implementations for modern languages and switched to something lower level all the time, we would still be using Fortran for business applications.

We still are using FORTRAN for Business Applications and I fail to see the need to switch them to a slower language to modernize them. Unless the switch is solving a program leave them alone. This is why in R there is still plenty of FORTRAN code. Personally I LOVE Python but I always feel it is the 2nd best choice. I do use Python but it rarely is the best tool to use for the problem you are solving. Maybe Pypy will…

I don't understand numerical analysis as business applications.

For me business applications are what you would use Cobol, Clipper, Java, Delphi, C#, Eifel, ....

Of course Fortran makes sense for number crushing, but that is the language domain, not doing CRUD, ETL or distributed computing stuff (not counting MPI here).

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#56
post #41
post #8

Earlier quoted context omitted.

> But bottom line, tons of python code out there needs more performance and has no dependency on numpy or any C extensions. What they need is nice JIT engines like PyPy and not to switch languages. If no one invested in improving implementations for modern languages and switched to something lower level all the time, we would still be using Fortran for business applications.

We still are using FORTRAN for Business Applications and I fail to see the need to switch them to a slower language to modernize them. Unless the switch is solving a program leave them alone. This is why in R there is still plenty of FORTRAN code. Personally I LOVE Python but I always feel it is the 2nd best choice. I do use Python but it rarely is the best tool to use for the problem you are solving. Maybe Pypy will…

R != Business Application.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#57

> 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…

Did you tell them that you wanted to contribute, rather than get a bug fixed?

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#58
post #5

Kudos 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...

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#59
post #8
post #5

Kudos 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…

> But bottom line, tons of python code out there needs more performance and has no dependency on numpy or any C extensions. What they need is nice JIT engines like PyPy and not to switch languages. If no one invested in improving implementations for modern languages and switched to something lower level all the time, we would still be using Fortran for business applications.

[deleted]

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#60
post #5

Kudos 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...

Yes - it's getting there and you can help it get there sooner by donating http://pypy.org/py3donate.html
Post reply on HN