[Biopython-dev] Changed in C API

[Dragoslav Zaric]

Ok Peter,

First it is my mistake that I was talking about python code upgrade. I
understand
that you want me to do C code upgrade, but at the end all should work
together so this
is why I looked at overall upgrade process.

I have downloaded latest python source code and I have searched for .c
files and .h files
and this is what I have found:

Bio\Cluster\cluster.c
Bio\Cluster\clustermodule.c
Bio\cMarkovModelmodule.c
Bio\cpairwise2module.c
Bio\csupport.c
Bio\KDTree\KDTree.c
Bio\KDTree\KDTreemodule.c
Bio\Motif\_pwm.c
Bio\Nexus\cnexus.c
Bio\PDB\mmCIF\lex.yy.c
Bio\PDB\mmCIF\mmcif_test.c
Bio\PDB\mmCIF\MMCIFlexmodule.c
Bio\trie.c
Bio\triemodule.c

Bio\Cluster\cluster.h
Bio\csupport.h
Bio\KDTree\KDTree.h
Bio\KDTree\Neighbor.h
Bio\trie.h

Are these all files you want me to upgrade to python 3.1 ?

Kind regards

On Tue, Oct 26, 2010 at 12:47 PM, Peter <biopython at maubp.freeserve.co.uk> wrote:
> On Tue, Oct 26, 2010 at 8:34 AM, Dragoslav Zaric
> <zaricdragoslav at gmail.com> wrote:
>> Dear Peter,
>>
>> The list of changes in Python 3 is not complete. This is current list:
>> ...
>>
>> Can you tell me what are exactly versions that we are converting, from
>> 2.7 to 3.0.1 ??
>
> We currently support Python 2.4 to 2.7 (but plan to drop support
> for Python 2.4 soon). We've been testing on Python 3.1 and except
> to support later versions as they are released.
>
> I personally don't really care about Python 3.0 (it would be nice if
> that works too, but it is not essential).
>
>> This means that python 3 is still no optimized or like all software
>> start to be worse with new versions :)
>
> Python 3.1 is already out and is faster than Python 3.0. Some things
> are still slower than Python 2 though, in particular we've noticed this
> for parsing since by default Python 3 uses unicode instead of byte
> strings.
>
> Peter
>



-- 
Dragoslav Zaric

Professional Programmer
MSc Astrophysics