-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/05/2011 11:56 AM, Jeremy Dunck wrote: > Carl, to be clear, if py3 pg is slower, but py2 pg is still in line w/ > baseline, would that block merge to trunk? It's quite possible the > problem lies in psycopg, but I think merging (with caveat emptor on > the py3/pg combination) would still be good.
Yeah, I agree. If there's no regression on py2 with the branch (which seems to be the case given Anssi's rough data), then slow py3 is certainly better than no py3. Though if its really ten-fold-plus slower, that would make py3/pg pretty much unusable, depending whether its something that's particularly bad in the test suite or that would affect typical code similarly. This is of course all uninformed hypothetical speculation :-) Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7dFnQACgkQ8W4rlRKtE2cKmQCeJWaMv8xQ+OERPYGl6bZ7tv8H vzcAn3zz0W26OxpDCoPf+tF/oOY33gh5 =qR3p -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
