On 5 February 2014 19:05, Thomas Goirand <zigo@debian.org> 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 Future class, and having another future module that isn't remotely related.
At least now we know it is something to watch out for.