Re: Adding python3-biopython
Hi Peter,
thanks for the hint. In principle it is better to open a bug report via
reportbug (I guess at least the user who requested this is running a
Debian system otherwise he would not have asked for it), but we try to
care for this.
Philipp, please drop a note if you have time constraints. Technical
hint: I have noted that you recently switched to CDBS. As far as I
understood the Python policy it is best practice to use dh with
dh_python2 and dh_python3 to easily accomplish what Peter is requesting.
Kind regards
Andreas.
On Mon, Mar 03, 2014 at 02:08:52PM +0000, Peter Cock wrote:
> Hello Philipp & DebianMed,
>
> The last few releases of Biopython supported Python 3
> via 2to3, but as of Biopython 1.63 (released December
> 2013) we have a single codebase which works on both
> Python 2.6/2.7 and Python 3.3+.
>
> Prompted by a user-query on Twitter, I looked into the
> Python 3 packages for Biopython/NumPy and the guidelines
> here https://wiki.debian.org/Python/Packaging which say
> Python 2.X and Python 3.X should be treated separately
> (using the prefix python3 rather than python).
>
> e.g. Python 2:
>
> https://packages.debian.org/sid/python-numpy
> http://packages.ubuntu.com/trusty/python-numpy
>
> https://packages.debian.org/sid/python-biopython
> http://packages.ubuntu.com/trusty/python-biopython
>
> vs. Python 3:
>
> https://packages.debian.org/sid/python3-numpy
> http://packages.ubuntu.com/trusty/python3-numpy
>
> We're missing a proposed python3-biopython package
> (which would need python3-numpy and Python 3.3+).
>
> Would this be straightforward to add please?
>
> Thanks,
>
> Peter
> (On behalf of the Biopython project)
>
>
> --
> To UNSUBSCRIBE, email to debian-med-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] CAKVJ-_5=ReCAPRxc57M_rQfDFP3wRLP7SMkDHsoC-=MySTmOwA@mail.gmail.com">https://lists.debian.org/[🔎] CAKVJ-_5=ReCAPRxc57M_rQfDFP3wRLP7SMkDHsoC-=MySTmOwA@mail.gmail.com
>
>
--
http://fam-tille.de
Reply to: