Message110324
| Author | pitrou |
|---|---|
| Recipients | belopolsky, brett.cannon, christian.heimes, grahamd, gvanrossum, ncoghlan, pitrou |
| Date | 2010-07-14.20:03:38 |
| SpamBayes Score | 0.00151336 |
| Marked as misclassified | No |
| Message-id | <1279137815.3128.13.camel@localhost.localdomain> |
| In-reply-to | <AANLkTimY91VkA4vpET-1KEgmz6HG2Q17P61-bi9j5n1H@mail.gmail.com> |
| Content | |
|---|---|
> That's why I said we should supply a context decorator (or function) which > will handle the lock appropriately, taking the name of the module to import > as an argument so the locking is fine-grained. Ok, so what are you saying is that we can break compatibility for non thread-safe import loaders which currently work fine? (I have nothing against it, just trying to be sure we agree on the implications) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-07-14 20:03:40 | pitrou | set | recipients: + pitrou, gvanrossum, brett.cannon, ncoghlan, belopolsky, christian.heimes, grahamd |
| 2010-07-14 20:03:38 | pitrou | link | issue9260 messages |
| 2010-07-14 20:03:38 | pitrou | create | |