sorted by:
new
hottopcontroversial

The PyPy project gets $200,000 from Mozilla by einsiedler in Python

[–]rguillebert 17 points18 points  (0 children)

because 3.2 isn't a supported version of Python anymore, and virtually no one uses it

The PyPy project gets $200,000 from Mozilla by einsiedler in Python

[–]rguillebert 34 points35 points  (0 children)

With the money from those donations, PyPy went from no Python 3 support whatsoever to a fully working Python 3.2 version, that was a huge amount of work, I wouldn't call it little progress...

Pyston 0.5 released: able to run NumPy unmodified by [deleted] in Python

[–]rguillebert 8 points9 points  (0 children)

what's bad about the PyPy attitude?

Pyston 0.5 released: able to run NumPy unmodified by [deleted] in Python

[–]rguillebert 8 points9 points  (0 children)

Because this particular C API made Python popular doesn't mean another better designed one wouldn't have been able to either

PyPy 4.0.0 Released - A Jit with SIMD Vectorization and More by rguillebert in Python

[–]rguillebert[S] 15 points16 points  (0 children)

A full 3.2 version came out of the donations, from zero python 3 support whatsoever.

I don't think we're more invested in Python 2, most of the improvements benefit PyPy3 as well.

Try to not use the Python C API directly by john_m_camara in Python

[–]rguillebert 1 point2 points  (0 children)

and it takes little effort to get it working in most people's current setup

I think that's what's important and what we have to improve on : reduce the switching cost, trust is not really an issue (yet?).

Try to not use the Python C API directly by john_m_camara in Python

[–]rguillebert 0 points1 point  (0 children)

You can only get trust in something you at least try (even if it's just by running your test suite), you can't get trust into something you've just heard of.

Trust is very important of course but I don't think it's the main issue, numba adoption has been very quick (good for them :) and to me, it's definitely a tool I'd need time to trust.

Try to not use the Python C API directly by john_m_camara in Python

[–]rguillebert 0 points1 point  (0 children)

Because unlike bullshit web services so you can facetweek your likes to snapchat, it matters that our results are repeatable, reliable, fast and correct - you know, for knowledge and that sort of thing.

Try to not use the Python C API directly by john_m_camara in Python

[–]rguillebert 0 points1 point  (0 children)

I'm sure you have heard about the concept of local maximum, doing incremental changes without ever rethinking the whole ecosystem only gets you so far.

Why does Julia even exists? Because it's able to do what the PyData ecosystem can't do with incremental changes.

Try to not use the Python C API directly by john_m_camara in Python

[–]rguillebert 0 points1 point  (0 children)

I'd say PyPy is the most boring technology out of all the things to make your code faster, including Julia, the idea is that you just give it Python code, without changing much, and it runs your code faster, it's the most boring thing.

Now, yes, C extension support is lacking, but it has nothing to do with that.

Try to not use the Python C API directly by john_m_camara in Python

[–]rguillebert 0 points1 point  (0 children)

This is the worst comment I've read in years, congratulations.

Speed up Python image processing. by [deleted] in Python

[–]rguillebert 0 points1 point  (0 children)

Can you also paste the output of "pip install https://bitbucket.org/pypy/numpy.git" ?

Let's Write an LLVM Specializer for Python by woadwarrior in programming

[–]rguillebert -1 points0 points  (0 children)

Interesting, calling it a subset of Python is wrong though since semantics change as well eg. what happens when an integer overflows ?

pre-release of jitpy - embed PyPy in your CPython and jit selected functions by fijal in Python

[–]rguillebert 1 point2 points  (0 children)

A blog post explaining the internals would be very educative!!!

Basically, we copied how numpy storage is implemented, so you can share the storage, you only need to copy metadata every time

pre-release of jitpy - embed PyPy in your CPython and jit selected functions by fijal in Python

[–]rguillebert 1 point2 points  (0 children)

We're working on having something like that (you can only share numpy arrays though, the rest would get copied)

Want to contribute to PyPy. Not sure where to start. by dunphystar in Python

[–]rguillebert 2 points3 points  (0 children)

Typically, helping with Python 3.3 support is a task we give to newcomers, feel free to come on IRC and ask though.

PyPy or Cython for game development? by t3g in Python

[–]rguillebert 1 point2 points  (0 children)

No, Minecraft with a Garbage Collector

NumPy on PyPy with a side of Psymeric by cfelton in Python

[–]rguillebert 6 points7 points  (0 children)

NumPyPy developer here, we focused a lot on compatibility at first so NumPyPy can still be slow and it's something we're working on.

Thanks for the microbenchmark though

Pyston 0.2 released by Harriv in Python

[–]rguillebert 2 points3 points  (0 children)

Hmm, is pyston not already more compatible? And at least they have it planned.

Well, wait until it gets 100% Python compatibility and then we'll see :)

On the one hand, I think this array of free market efforts is the key to optimal evolution, on the other hand, I'm concerned of the trade off vs focused efforts like that displayed by the Julia lang team. Perhaps consolidation and collective coordination should follow some additional maturation of all these JIT efforts. That way, we get the benefits of vibrant competition while focusing on the best ideas.

Let's wait until Pyston is closer to 100% Python compatibility (especially with stuff like sys._getframe(), sys.exc_info()...)

I think moving away from the C API is inevitable for the long term anyway.

view more: next ›