On Thu, Apr 4, 2013 at 1:25 AM, Alex Gaynor wrote:
> Not your fault, those occur on default as well. I don't know of any way to
> get better messages.
>
> Alex
The problem is that in dicts (rpython dicts responsible for
W_DictObject and W_SetObject), we want to know that keys are non-null.
We alr
Not your fault, those occur on default as well. I don't know of any way to
get better messages.
Alex
On Wed, Apr 3, 2013 at 4:20 PM, wrote:
> Hi,
>
> say I have something like this during translation:
>
> [rtyper:WARNING] SomeInstance(can_be_None=True, classdef=pypy.interpreter.
> **baseobjspa
Hi,
say I have something like this during translation:
[rtyper:WARNING] SomeInstance(can_be_None=True,
classdef=pypy.interpreter.baseobjspace.W_Root) can be null, but forcing
non-null in dict key
[rtyper:WARNING] SomeInstance(can_be_None=True,
classdef=pypy.interpreter.baseobjspace.W_Root) ca
On Wed, Apr 3, 2013 at 1:38 PM, Antonio Cuni wrote:
> On 04/03/2013 09:27 AM, Maciej Fijalkowski wrote:
>>
>> hello everyone
>>
>> I'm incredibly unhappy about the 2.7 -> 2 lib rename. It broke
>> virtualenv, there is no recent virtualenv available and there is
>> absolutely no good reason why we
> +1, although to jumpy to the defence of whoever did the commit, it's not
> obvious that such a change breaks virtualenv because there are not
> tests.
> Maybe we should setup a buildbot to run virtualenv's tests with the
> nightly pypy?
> I didn't do that when I added virtualenv support for the s
On 04/03/2013 09:27 AM, Maciej Fijalkowski wrote:
hello everyone
I'm incredibly unhappy about the 2.7 -> 2 lib rename. It broke
virtualenv, there is no recent virtualenv available and there is
absolutely no good reason why we did that. I'm now spending tons of
time trying to think how to update
Hi Fijal,
On Wed, Apr 3, 2013 at 9:36 AM, Maciej Fijalkowski wrote:
>> I'm incredibly unhappy about the 2.7 -> 2 lib rename. It broke
>> virtualenv, (...)
As far as I'm concerned, it can be renamed back. "It's because of
Python 3" is not really a good enough argument to start with, but if
it br
On Wed, Apr 3, 2013 at 9:27 AM, Maciej Fijalkowski wrote:
> hello everyone
>
> I'm incredibly unhappy about the 2.7 -> 2 lib rename. It broke
> virtualenv, there is no recent virtualenv available and there is
> absolutely no good reason why we did that. I'm now spending tons of
> time trying to th
hello everyone
I'm incredibly unhappy about the 2.7 -> 2 lib rename. It broke
virtualenv, there is no recent virtualenv available and there is
absolutely no good reason why we did that. I'm now spending tons of
time trying to think how to update virtualenv to a TOT version a bit
everywhere.
I'm i
