Message196813
| Author |
eli.bendersky |
| Recipients |
eli.bendersky, ezio.melotti, ncoghlan, serhiy.storchaka |
| Date |
2013年09月02日.21:52:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAF-Rda9Xxwx2M7p0w_vm7N-u-B4pMrd7ZzN4C1kRG=JHGLRQqw@mail.gmail.com> |
| In-reply-to |
<CADiSq7fMZ9n518zhOLFLY6ce29+hiQ57wuPqU71cN0MoJ+4qkw@mail.gmail.com> |
| Content |
> An easier hack is likely just a new "always run in subprocess" container
> with submodule names in regrtest.py. It's not elegant, but it will work.
>
True, that's also an option. I had it in mind in the beginning, but it's
too hacky for my tastes :-) Not doing state-changing stuff in the global
scope is a good practice anyway, so the restriction should be too horrible.
Do we have some sort of conventions of outside-discoverable module
attributes (like the __REGRTEST_SUBPROCESS__ proposed above)? I.e. in terms
of naming, type, expected values? |
|