On Sep 15, 2014, at 4:34 AM, Lucas Alvares Gomes wrote:
> So, although I like the fix proposed and I would +1 that idea, I'm
> also not very concerned if most of the people don't want that. Because
> as you just said we can fix it locally easily. I didn't set it to my
> .local but the way I do n
On Sep 15, 2014, at 7:34 AM, Lucas Alvares Gomes wrote:
>
> So this ordering thing, I don't think that it's caused by the
> PYTHONDONTWRITEBYTECODE, I googled that but couldn't find anything
> relating this option to the way python hash things (please point me to
> a document/code if I'm wrong)
Hi Mike,
Thanks for bringing it up. I wanna say that I'm not an expert in
CPython, but I personally like the fix because I have had some
problems with stale .pyc in Ironic before, and they are pretty
annoying.
On Fri, Sep 12, 2014 at 4:18 PM, Mike Bayer wrote:
> I’ve just found https://bugs.laun
On Fri, Sep 12 2014, Mike Bayer wrote:
> Just my 2.5c on this issue as to the approach I think is best. Leave
> the Python interpreter’s behavior as much as “normal” as possible in
> our default test environment.
I definitely agree with all of that. :)
--
Julien Danjou
// Free Software hacker
/
I’ve just found https://bugs.launchpad.net/nova/+bug/1368661, "Unit tests
sometimes fail because of stale pyc files”.
The issue as stated in the report refers to the phenomenon of .pyc files that
remain inappropriately, when switching branches or deleting files.
Specifically, the kind of scenar
