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
[CC me please]
Dear all,
I am trying to build a python3 package from an existing package:
openslide-python.
After following recommendations from:
https://wiki.debian.org/Python/LibraryStyleGuide
Here is what I get:
http://packages.debian.org/sid/all/python3-openslide/filelist
clearly it
On 02/01/2014 04:10 PM, PICCA Frederic-Emmanuel wrote:
> Hello,
>
> I am packaging the next version of spyder which is a python IDE.
> The next version will support python3
>
> so I need to add a spyder3 binary package which will contain
> /usr/bin/spyder3
>
> the upstream script only create /us
On Wed, Feb 05, 2014 at 04:16:06PM +0800, Thomas Goirand wrote:
> Hi,
Hello
>
> Thanks for raising this important topic.
>
> What I've been doing up to now, is renaming "foo" into "python3-foo" and
> "python2-foo", then I use update-alternatives to provide /usr/bin/foo,
> with the python2 versi
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
[Mathieu Malaterre, 2014-02-05]
> [CC me please]
>
> Dear all,
>
> I am trying to build a python3 package from an existing package:
> openslide-python.
> After following recommendations from:
>
> https://wiki.debian.org/Python/LibraryStyleGuide
>
> Here is what I get:
>
> http://packages
PICCA Frederic-Emmanuel
writes:
> I am packaging the next version of spyder which is a python IDE.
Thanks for working to package useful software for Debian.
> The next version will support python3
> so I need to add a spyder3 binary package which will contain
> /usr/bin/spyder3
This implies (b
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 Wed, Feb 05, 2014 at 08:07:59PM +1100, Ben Finney wrote:
> > The next version will support python3
> > so I need to add a spyder3 binary package which will contain
> > /usr/bin/spyder3
>
> This implies (because you're naming the binary differently) that the new
> version will have features *inc
9 matches
Mail list logo
