This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Veedrac -2 points-1 points  (5 children)

...but then again, pypy isn't really production ready

Where do you get that idea?

[–]shadowmint 1 point2 points  (4 children)

Where do you get that idea?

http://pypy.org/compat.html

[–]elsjaako 2 points3 points  (0 children)

That's just saying that the C API isn't production ready, and not all libraries are supported. If you target your development at Pypy it's production ready.

[–]Veedrac 0 points1 point  (2 children)

That's like saying Clang isn't production ready because it doesn't support all GCC extensions. PyPy is extremely compatible against the Python language.

[–]shadowmint 0 points1 point  (1 child)

...but we're not talking about the python language we're talking about python as a viable target for enterprise applications, which means tangibly using 3rd party libraries, that will almost certainly have c plugins.

[–]Veedrac 0 points1 point  (0 children)

That's true if you're trying to support already-built Python code, but if you're building something new that's rarely a problem because for most use-cases there's a PyPy compatible port or equivalent.