nebfa - Fasta File Parser
Usage:
>>> import nebfa >>> rec = nebfa.parse(open("./test/data/basic.fa")).next() >>> rec.id ('gi', '0120123123') >>> rec.desc 'Some stuff' >>> rec.sequence 'ACGT' >>> rec.hash '2108994E17F6CCA9FF2352ADA92B6511DB076034'# Alternatively, parse_file avoids the need for a call to open. >>> for rec in nebfa.parse_file(“./test/data/multi.fa”): … print rec.id (‘gi’, ‘0120123123’) (‘ref’, ‘YP_234234.2’)
Records also have a meta attribute that has two keys for identifiers and descriptions. You will need to consult that member when you have Ctl-A separated deflines. If you have a better syntax suggestion please send a note along.
Metadata
Release files for nebfa 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nebfa-0.0.2.tar.gz | 9.4 kB | Without provenance | Details for nebfa-0.0.2.tar.gz |
Release files / nebfa-0.0.2.tar.gz
| Download URL | nebfa-0.0.2.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3738b8174d895ca1f4dbde7e1e765bd6b743a0d2b8ea91c9bbca393333bb101a
|
|
BLAKE2b-256 checksum How to use checksums |
17e3802f5c46c8ef8eb63ebb214760c20906afd629e571f8f6d5fd74d4442924
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nebfa 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.