Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chromosomes are everywhere- should they be? #345

Open
adf-ncgr opened this issue Dec 3, 2022 · 1 comment
Open

chromosomes are everywhere- should they be? #345

adf-ncgr opened this issue Dec 3, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@adf-ncgr
Copy link
Contributor

adf-ncgr commented Dec 3, 2022

@alancleary just noticed that I inherited something from your setup.cfg that doesn't seem to make a lot of sense:

[options.entry_points]
console_scripts =
    chromosome = search.__main__:main

it probably doesn't actually matter, but the occurrence of "chromosome" in this and all other microservices setup.cfg files that are not in fact the chromosome microservice seems like it's probably a minor goof

@alancleary
Copy link
Collaborator

Good catch! Clearly we're not using the CLI support that this adds to each microservice. It's still worth fixing, though. Perhaps it's worth putting a test in place to make sure this is right...

@alancleary alancleary self-assigned this Dec 5, 2022
@alancleary alancleary added the bug Something isn't working label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants