Message160150
| Author | eric.snow |
|---|---|
| Recipients | Arfrever, brett.cannon, eric.araujo, eric.smith, eric.snow, lemburg, ncoghlan, pitrou, python-dev |
| Date | 2012-05-07.15:23:04 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1336404185.35.0.781702256856.issue14657@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm +1 on Nick's recommendation. @Antoine > Ideally, we would want to test both versions, so that any oddity in > the freezing mechanism gets exercised and diagnosed properly. +1 Does this mean that the whole test suite should be run under both (whenever _bootstrap.py is modified)? Would that warrant a new flag for the test suite or even an automated check? That's what I was getting at with this: > 1. python starts up normally. > 2. we clear out all the entire import state except for builtins. > 3. we stick importlib._bootstrap in place. > 4. we set builtins.__import__ to importlib.__import__. > 5. we re-populate sys.modules by reloading all the modules that > were in there before (?). > 6. we run the test suite against this new import state. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-05-07 15:23:05 | eric.snow | set | recipients: + eric.snow, lemburg, brett.cannon, ncoghlan, pitrou, eric.smith, eric.araujo, Arfrever, python-dev |
| 2012-05-07 15:23:05 | eric.snow | set | messageid: <1336404185.35.0.781702256856.issue14657@psf.upfronthosting.co.za> |
| 2012-05-07 15:23:04 | eric.snow | link | issue14657 messages |
| 2012-05-07 15:23:04 | eric.snow | create | |