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

Allow reference sequence to be returned always as upper case. #71

Merged
merged 8 commits into from
Jul 29, 2015

Conversation

mattions
Copy link

This is just a merge request to allow to return the sequence always as upper case, both in the raw and in the sequence format.

We have this user case in our case.

@landscape-bot
Copy link

Code Health
Repository health increased by 0.15% when pulling 9e24c20 on mattions:allow_always_uppercase_seq into cd0fdea on mdshw5:master.

@mdshw5
Copy link
Owner

mdshw5 commented Jul 29, 2015

Thanks for the pull request. If you add a test case for this (maybe here) then I'll merge and push a new PyPI release. It would also be great if you document this feature in the Readme.

@mattions
Copy link
Author

As data tests,
is ok if I add a small bit of the hs37d5 in the data repo, or should I download the whole thing from somewhere and add it to the download_gene_fasta.py ?

I'm downloading the gens right now, if there is already an example with smaller case I could use that directly.

mdshw5 added a commit that referenced this pull request Jul 29, 2015
Make a copy of genes.fasta called "genes.fasta.lower" for #71 test case.
@mdshw5
Copy link
Owner

mdshw5 commented Jul 29, 2015

The script that generates the test data now generates a file called "genes.fasta.lower". This file should work for testing your contribution. You don't even have to test against a particular sequence, you could:

assert Fasta(sequence_always_upper=True)['gi|557361099|gb|KF435150.1|'] == Fasta()['gi|557361099|gb|KF435150.1|'].seq.upper()

and do the same for the as_raw case.

@mattions
Copy link
Author

@mdshw5 I have updated the test to use genes.fasta.lower (and also make sure it gets created if you do not have it on the disk already.)

README updated with the example.

Should go green.

mdshw5 added a commit that referenced this pull request Jul 29, 2015
Allow reference sequence to be returned always as upper case.
@mdshw5 mdshw5 merged commit a4904b9 into mdshw5:master Jul 29, 2015
@mdshw5
Copy link
Owner

mdshw5 commented Jul 29, 2015

Looks great - thanks for the contribution!

@mattions
Copy link
Author

mattions commented Aug 3, 2015

do you have an idea when the next release with this fix will be out?

mdshw5 added a commit that referenced this pull request Aug 3, 2015
@mdshw5
Copy link
Owner

mdshw5 commented Aug 3, 2015

Thanks for reminding me. I just pushed the release through CI. When the tests pass a new version will be pushed to PyPI. Should happen some time this morning.

On Aug 3, 2015, at 7:18 AM, Michele Mattioni [email protected] wrote:

do you have an idea when the next release with this fix will be out?


Reply to this email directly or view it on GitHub.

@mdshw5
Copy link
Owner

mdshw5 commented Aug 3, 2015

Looks like it's done.

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

Successfully merging this pull request may close these issues.

3 participants