Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #62756 > unrolled thread
| Started by | Jason Friedman <jsf80238@gmail.com> |
|---|---|
| First post | 2013-12-26 17:15 -0700 |
| Last post | 2013-12-26 17:15 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Getting updates and restarting a long running url request. Jason Friedman <jsf80238@gmail.com> - 2013-12-26 17:15 -0700
| From | Jason Friedman <jsf80238@gmail.com> |
|---|---|
| Date | 2013-12-26 17:15 -0700 |
| Subject | Re: Getting updates and restarting a long running url request. |
| Message-ID | <mailman.4641.1388103358.18130.python-list@python.org> |
> Would this not keep requesting/submitting additional (duplicate) BLAST > queries? >> >> try: >> this_result = get_BLAST(id) >> result_dict[id] = True > I assumed that NCBIWWW.qblast waits for a response from the server. Are you saying that instead it queues a request, and the NCBIXML.read(blast_result) command fetches the result? > > That said after some more research I found this tread. > http://lists.open-bio.org/pipermail/biopython/2013-April/008507.html I read that post to say that you will be submitting one request for a lot of data points that you will then need to parse, is that true?
Back to top | Article view | comp.lang.python
csiph-web