Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Any potential clash with biopython #249

Open
mauriceling opened this issue Dec 9, 2021 · 2 comments
Open

Any potential clash with biopython #249

mauriceling opened this issue Dec 9, 2021 · 2 comments

Comments

@mauriceling
Copy link

Hi,

I am a little concerned with the import statement "from bio import *" as it is too similar to that of using Biopython - "from Bio import *"

@markhend
Copy link
Collaborator

Hi @mauriceling,

Thanks for pointing this out. Are there specific name clashes you've experienced? I was trying to think through a scenario where the Seq language bio module may conflict with biopython or vice versa. I think biopython could be used successfully from within Seq if desired. e.g.

@python
def test_Bio():
    from Bio import Seq as pySeq  # importing from biopython
    my_seq = pySeq.Seq("CATGTAGACTAG")
    print(my_seq)
test_Bio()

Seq does not allow import * from Python modules.

@mauriceling
Copy link
Author

Hi @markhend

OK, perhaps it is not a clash but the name is definitely inviting errors for a dyslexic person like me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants