Message249092
| Author |
njs |
| Recipients |
Arfrever, barry, berker.peksag, brett.cannon, eric.snow, josh.r, jwilk, larry, ncoghlan, njs, serhiy.storchaka, takluyver |
| Date |
2015年08月25日.00:40:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1440463243.08.0.334357745685.issue24305@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
You're right, "impossible" is a slight exaggeration :-). As an alternative, every package could indeed carry around a table containing the details of importlib's call stack in every version of Python.
(I also haven't checked whether it's consistent within a single stable release series. I guess we could add a rule that 3.5.x -> 3.5.(x+1) cannot change the number of function calls inside the importlib callstack, because that is part of the public API, but I have less than perfect confidence that this rule has been enforced strictly in the past, and I don't think I'd want to be the one in charge of enforcing it in the future.) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年08月25日 00:40:43 | njs | set | recipients:
+ njs, barry, brett.cannon, ncoghlan, larry, jwilk, Arfrever, eric.snow, takluyver, berker.peksag, serhiy.storchaka, josh.r |
| 2015年08月25日 00:40:43 | njs | set | messageid: <1440463243.08.0.334357745685.issue24305@psf.upfronthosting.co.za> |
| 2015年08月25日 00:40:43 | njs | link | issue24305 messages |
| 2015年08月25日 00:40:42 | njs | create |
|