Re: [pypy-dev] Playing with PyPy and Django

2015-02-06 Thread Maciej Fijalkowski
PyPy 3 is definitely slower than PyPy 2 btw, just so you know On Sat, Feb 7, 2015 at 8:56 AM, Omer Katz wrote: > You need to warm up the JIT first. > Run the benchmark a 10,000 times on PyPy before measuring and you'll see the > real performance improvement. > Nevertheless, it does sound like you

Re: [pypy-dev] Playing with PyPy and Django

2015-02-06 Thread Omer Katz
You need to warm up the JIT first. Run the benchmark a 10,000 times on PyPy before measuring and you'll see the real performance improvement. Nevertheless, it does sound like you're hitting a performance bug(s) somewhere. It's worth investigating. 2015-02-07 1:12 GMT+02:00 Tin Tvrtković : > Hello

[pypy-dev] Playing with PyPy and Django

2015-02-06 Thread Tin Tvrtković
Hello, PyPy folks! While trying to speed up one of my Django sites, I noticed a new version of PyPy had just been released. So I grabbed a fresh download of PyPy 3 (since this is a Python 3 codebase) and tried taking it out for a spin. However, as far as I can see, whatever I try PyPy is cons

[pypy-dev] Fwd: [pypy-commit] pypy default: Rename the --output option to --really-force-output, and document it

2015-02-06 Thread Armin Rigo
Hi Tobias, (answering an off-list-by-mistake mail) On 6 February 2015 at 13:50, Tobias Pape wrote: > So this is changed in rpython for a pypy issue? Yes, someone else made the same point on IRC. I have now reverted this change, and added a check to "targetpypystandalone.py" that you don't try

Re: [pypy-dev] Windows: pypyw.exe?

2015-02-06 Thread Amaury Forgeot d'Arc
2015-02-06 11:27 GMT+01:00 Armin Rigo : > Hi, > > On 6 February 2015 at 11:15, Amaury Forgeot d'Arc > wrote: > > This has other implications. > > For example, sys.stdout points to an invalid file descriptor, > > and I remember that old versions of pythonw.exe used to freeze after > > printing 819

Re: [pypy-dev] [pypy-commit] pypy default: Rename the --output option to --really-force-output, and document it

2015-02-06 Thread Armin Rigo
Hi Fijal, On 6 February 2015 at 09:54, Maciej Fijalkowski wrote: > This change breaks places that recommend you to use --output (e.g. > check that you're not translating with the same executable) Grepping for "--output", I can find only translate.py that says "use --output=..." so I'll guess you

Re: [pypy-dev] Windows: pypyw.exe?

2015-02-06 Thread Armin Rigo
Hi, On 6 February 2015 at 11:15, Amaury Forgeot d'Arc wrote: > This has other implications. > For example, sys.stdout points to an invalid file descriptor, > and I remember that old versions of pythonw.exe used to freeze after > printing 8192 characters. I'm not finding anything special done wit

Re: [pypy-dev] Windows: pypyw.exe?

2015-02-06 Thread Amaury Forgeot d'Arc
2015-02-06 3:34 GMT+01:00 Yaacov Finkelman : > The difference between pythonw.exe and python.exe is that one is a > "windows" application and the other is a "console" application. > This has other implications. For example, sys.stdout points to an invalid file descriptor, and I remember that old

Re: [pypy-dev] [pypy-commit] pypy default: Rename the --output option to --really-force-output, and document it

2015-02-06 Thread Maciej Fijalkowski
This change breaks places that recommend you to use --output (e.g. check that you're not translating with the same executable) On Thu, Feb 5, 2015 at 5:52 PM, arigo wrote: > Author: Armin Rigo > Branch: > Changeset: r75726:babfa1dd27a5 > Date: 2015-02-05 16:51 +0100 > http://bitbucket.org/pypy/p

Re: [pypy-dev] Faulty binary 2.5.0 package(s) on bitbucket download page

2015-02-06 Thread Matti Picus
On 06/02/15 09:48, Matti Picus wrote: Somehow the binary package of linux64 on the bitbucket download page https://bitbucket.org/pypy/pypy/downloads contained a different libpypy-c.so than the source on http://buildbot.pypy.org/nightly/r