Brian May writes:
> Not a problem. It is rather confusing situation - having a module
> renamed from futures to concurrent.futures that contains a Future
> class, and having another future module that isn't remotely related.
For my part, I think the name “futures” is far too generic a name to us
On 5 February 2014 19:05, Thomas Goirand wrote:
> Just a quick message to say sorry for being the source of this big
> confusion between future and futures (with "s").
>
Not a problem. It is rather confusing situation - having a module renamed
from futures to concurrent.futures that contains a F
On 02/05/2014 06:04 AM, Brian May wrote:
> Hello,
>
> Has anybody considered packaging python-future for Debian?
>
> No, I am not talking about python-futures, python-concurrency.futures,
> or anything relating to #736523 (the first message in this bug had
> rather confused at first).
>
> Rather
Hello,
Has anybody considered packaging python-future for Debian?
No, I am not talking about python-futures, python-concurrency.futures, or
anything relating to #736523 (the first message in this bug had rather
confused at first).
Rather I am talking about:
http://python-future.org/
"future is
4 matches
Mail list logo
