Bio::T...::Query(3pm)

πŸ“¦
version 1.77 Β· 4 versions
, in debian trixie, ubuntu resolute, ubuntu stonking

✨ Bio::Tools::EUtilities::Query ✨

okay bestie, listen up πŸ’– this is the Bio::Tools::EUtilities::Query page from the 3pm manual, and it's literally the pluggable lil module that handles all your query-related data. It's giving backend energy, and we're obsessed.


🌸 VERSION 🌸

version 1.77 β€” that's the one, no cap πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

not me telling you this but do NOT create an instance directly β€” Bio::Tools::EUtilities does that for you, periodt.
### should not create instance directly; Bio::Tools::EUtilities does this ###

# can also use '-response' (for HTTP::Response objects) or '-fh' (for
# filehandles)

my $info = Bio::Tools::EUtilities->new(-eutil => 'esearch',
                                       -file => 'esearch.xml');

# esearch

# esearch with history

# egquery

# espell (just for completeness, really)

so yeah β€” -response for your HTTP::Response objects, -fh for filehandles, -file for a file, you get the vibe 😌 the espell bit is just for completeness, really β€” her words not mine πŸ™ˆ


πŸ’œ DESCRIPTION πŸ’œ

Pluggable module for handling query-related data returned from eutils. That's it, that's the whole job description, and she does it flawlessly πŸ‘‘


πŸŽ€ Bio::Tools::EUtilities::Query methods πŸŽ€

⭐ to_string ⭐

Title    : to_string
Usage    : $foo->to_string()
Function : converts current object to string
Returns  : none
Args     : (optional) simple data for text formatting
Note     : Used generally for debugging and for the print_* methods

so like β€” you call $foo->to_string(), it turns your current object into a string πŸͺ„ it returns none, the args are optional and just for text formatting, and lowkey it's mostly for debugging and for the print_* methods. iykyk πŸ’«


🫢 FEEDBACK 🫢

πŸ’Œ Mailing lists πŸ’Œ

user feedback is an integral part of the evolution of this and other Bioperl modules β€” so like, your thoughts are the main character here, fr fr. send your comments and suggestions preferably to the Bioperl mailing list. your participation is much appreciated πŸ’–

bioperl-l@bioperl.org               - General discussion
https://bioperl.org/Support.html    - About the mailing lists

🌈 Support 🌈

please direct usage questions or support issues to the mailing list: bioperl-l@bioperl.org rather than to the module maintainer directly. many experienced and reponsive experts will be able look at the problem and quickly address it. please include a thorough description of the problem with code and data examples if at all possible. (yes the original says "reponsive", we're leaving that exactly as-is, character for character, no edits bestie πŸŽ€)

πŸ› Reporting bugs πŸ›

report bugs to the Bioperl bug tracking system to help us keep track of the bugs and their resolution. bug reports can be submitted via the web:

https://github.com/bioperl/bio-eutilities/issues

go off, report that bug, it's giving responsible πŸ‘‘


πŸ‘‘ AUTHOR πŸ‘‘

Chris Fields <cjfields@bioperl.org>


this software is copyright (c) 2006-2013 by Chris Fields.

this software is available under the same terms as the perl 5 programming language system itself.


πŸ’€ reminder bestie: don't construct this object yourself, let Bio::Tools::EUtilities do it. that's the whole vibe check. πŸ¦‹

and that's a wrap β€” perl v5.40.0, dated 2025-01-27, from the Bio::T...::Query(3pm) page. slay, stay hydrated, and go parse some eutils data πŸ’–βœ¨

πŸ“¦ where this page comes from