Re: Ideas for Biopython 2.0

Peter Cock <[email protected]> Mon, 19 Jun 2017 15:58:02 +0100
Newsgroups gmane.comp.python.bio.devel
Message-ID <CAKVJ-_5bQULNiWq9zEu7jT5iuY8SbNbRyB_Z3F2=AiwTHnQUTQ@mail.gmail.com>
Yep - that's what I meant :)

i.e. "biopython" (or "biopy" or ...") as a folder name meaning we'd
have for example "biopython/sequences/__init__.py`` which can
be import as "from biopython import sequences" etc.

The NumPy/SciPy like usage pattern for importing had crossed my
mind too - although if we try to minimise the top level automatic
imports I think that is less useful?

(By that I mean that for example people doing clustering would not
want the overhead of lots of sequence code being imported by default)

Peter

On Mon, Jun 19, 2017 at 3:47 PM, Tiago Antão <[email protected]> wrote:
> Or even
> biopython.*
> and have a recommendation of
> import biopython as bp
> Tiago
>
> On 19 June 2017 at 08:45, Peter Cock <[email protected]> wrote:
>>
>> I am generally in agreement with your comments Tiago.
>>
>> Note as per my reply to Patrick, we can't use "bio" (lower case)
>> as this would be the same directory on disk as "Bio" (title case) on
>> Windows and most Macs which use a case-insensitive file system.
>> Thus suggestions like "biopy" and "biopython" instead.
>>
>> Peter
>>

_______________________________________________
Biopython-dev mailing list
[email protected]
http://mailman.open-bio.org/mailman/listinfo/biopython-dev