Oops. I think I need more tests. I will post it under pygr-dev if I found
something serious.
On Tue, Nov 18, 2008 at 8:45 AM, Namshin Kim <[EMAIL PROTECTED]> wrote:
> Hi Chris,
>
> Now, I got another problem.
>
> >>> from pygr import seqdb
> >>> R1 = seqdb.BlastDB('R1')
> >>> R1.has_key('1')
> True
> >>> R1.has_key('1A') # EXTREMELY SLOW
>
> You can use the same BlastDB as previous test. Python does not show any
> increase of memory usage.
>
> Yours,
> Namshin Kim
>
>
> On Wed, Oct 22, 2008 at 9:48 AM, Namshin Kim <[EMAIL PROTECTED]> wrote:
>
>> Thanks everyone! I tested the new BlastDB and it works great.
>>
>> Namshin Kim
>>
>>
>>
>>
>> On Wed, Oct 22, 2008 at 4:56 AM, Christopher Lee <[EMAIL PROTECTED]>wrote:
>>
>>>
>>> I added a workaround for the shelve iterator problem (their iterator
>>> was loading the entire index into memory). Get the latest source from
>>> the public git repository.
>>>
>>> -- Chris
>>>
>>> >>>
>>>
>>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
