On Oct 21, 2008, at 6:54 PM, Namshin Kim wrote:

> And I ran all tests for Python 2.6 and found some errors. Megatest  
> has no errors for Python 2.6.
>
> ======== pygrtest_common.py error
> Traceback (most recent call last):
>   File "protest.py", line 12, in <module>
>     import pygrtest_common
>   File "/result/pygr_megatest/src_save/pygr/tests/ 
> pygrtest_common.py", line 21, in <module>
>     ver = ".".join(platform.python_version_tuple()[:2])
> TypeError: sequence item 0: expected string, int found

I guess they changed the python_version_tuple format...

> ======== fixes for pygrtest_common.py
> ver = ".".join(map(str, platform.python_version_tuple()[:2]))

Makes sense...

> ======== sequence_test.py error
> /result/pygr_megatest/src_save/pygr/build/lib.linux-x86_64-2.6/pygr/ 
> seqdb.py:309: DeprecationWarning:
> os.popen2 is deprecated.  Use the subprocess module.
>   ifile,ofile=os.popen2(cmd)

ignore for the moment.  Unfortunately subprocess was only introduced  
in Python 2.4.

>
> Traceback (most recent call last):
>   File "protest.py", line 123, in <module>
>     if do_test(sys.argv[2],sys.argv[3],sys.argv[4]):
>   File "protest.py", line 33, in do_test
>     m()
>   File "/result/pygr_megatest/src_save/pygr/tests/sequence_test.py",  
> line 88, in blast_test
>     minAlignSize=14,pIdentityMin=0.5)
>   File "pygr.cnestedlist.pyx", line 599, in  
> pygr.cnestedlist.NLMSASlice.edges
>   File "pygr.cnestedlist.pyx", line 831, in  
> pygr.cnestedlist.NLMSASlice.groupByIntervals
>   File "pygr.cnestedlist.pyx", line 882, in  
> pygr.cnestedlist.NLMSASlice.filterIvalConservation
> TypeError: 'dict' object doesn't support item deletion

This error message is puzzling.  The Python 2.6 docs explicitly  
support the use of del on a dict object:
"del d[key]
     Remove d[key] from d. Raises a KeyError if key is not in the map."

Also, it's hard to see how all the megatests could pass if such a  
basic language feature were removed in 2.6.  This message sounds like  
a bug to me... but whose bug?  My first guess is that this might be a  
Python 2.6 bug, since it's still quite new...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to