Message194835
| Author |
eli.bendersky |
| Recipients |
Arfrever, Robin.Schreiber, asvetlov, effbot, eli.bendersky, pitrou, python-dev |
| Date |
2013年08月10日.21:12:20 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAF-Rda-V_A11NwPFVJkw92OM34jocfXEKzXro50Fu2S1hDzw3A@mail.gmail.com> |
| In-reply-to |
<1376156314.2570.1.camel@fsol> |
| Content |
On Sat, Aug 10, 2013 at 10:38 AM, Antoine Pitrou <report@bugs.python.org>wrote:
>
> Antoine Pitrou added the comment:
>
> > Antoine, I committed your patch (with a bit of comments added),
> > *leaving the module caching in*.
>
> Thanks!
>
> > A longer term solution to all this will be
> > http://mail.python.org/pipermail/python-dev/2013-August/127766.html -
> > I want to eventually run all "monkey-patch the import environment to
> > simulate some situation" sub-tests of ET in different subprocesses to
> > they are kept independent.
>
> I find it useful that the test suite stresses module unloading or
> reloading. There's probably a bug either in ET or in the ET tests. I'm
> not saying it's a very important issue of course, but IMHO it would be
> better if we don't try to swipe it under the carpet :-)
>
I have no intention swiping things under the carpet. I'll get to the bottom
of this to understand the exact flow that causes this to happen.
But I still think ET tests should be logically separated into subprocesses.
If we want to stress test module unloading and reloading, let's have
specific, targeted tests for that. |
|