Message247879
| Author | alex.gronholm |
|---|---|
| Recipients | Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov |
| Date | 2015-08-02.15:56:48 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1438531008.94.0.694494072871.issue24383@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
You're right Stefan -- I too was appalled that this was not possible in 3.5 to begin with. It feels completely natural to be able to await for concurrent Futures. But as this is considered a feature, it'll probably have to wait until 3.6. Otherwise you'll end up your app requiring a specific micro-release which is a big no-no in the Python world, as far as features go at least. But if this is considered a bugfix, it could still go into 3.5.0... *wink wink*. That's what I'm hoping for of course. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-08-02 15:56:48 | alex.gronholm | set | recipients: + alex.gronholm, gvanrossum, scoder, vstinner, Yury.Selivanov, yselivanov |
| 2015-08-02 15:56:48 | alex.gronholm | set | messageid: <1438531008.94.0.694494072871.issue24383@psf.upfronthosting.co.za> |
| 2015-08-02 15:56:48 | alex.gronholm | link | issue24383 messages |
| 2015-08-02 15:56:48 | alex.gronholm | create | |