Reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736523#65
J On Wed, Feb 5, 2014 at 8:57 AM, Brian May <br...@microcomaustralia.com.au> wrote: > On 4 February 2014 08:57, Brian May <br...@microcomaustralia.com.au> wrote: >> >> After last night's talk on Python future, I decided to look up the status >> of packages for Debian. >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736523 >> >> Oops. Seems to have deteriorated into a silly argument over what teamwork >> means :-( > > > Looks like *everyone*, including myself, got a bit confused. > > This isn't python-future they are discussing, this is > python-concurrency.futures. > > http://docs.python.org/dev/library/concurrent.futures.html > > vs > > http://python-future.org/ > > It looks like the discussion with concurrent.futures continued on the > debian-python mailing list, and is now resolved. > > Discussion starts at > https://lists.debian.org/debian-python/2014/01/msg00044.html > -- > Brian May <br...@microcomaustralia.com.au> > > _______________________________________________ > melbourne-pug mailing list > melbourne-pug@python.org > https://mail.python.org/mailman/listinfo/melbourne-pug > _______________________________________________ melbourne-pug mailing list melbourne-pug@python.org https://mail.python.org/mailman/listinfo/melbourne-pug
