Patch to add support for python 3.x

[Baptiste Lepilleur]

I've put the patch on the tracker:
http://code.google.com/p/llvm-py/issues/detail?id=28

I've tested it with python 2.6.2 and python 3.1 on Windows.

Baptiste.

[Rohit Garg]

I assume it does not mess with LLVM's API's. I want to use it with r82
of llvm-py as I have LLVM 2.5.

ATM, there are 4 branches,

a) llvm 2.5 + py 2.6
b) llvm 2.5 + py 3.1
c) llvm 2.6 + py 2.6
d) llvm 2.6 + py 3.1

it might be a good idea to switch to a dvcs to maintain these branches.

I'd vote for git.

--
Rohit Garg

http://rpg-314.blogspot.com/

Senior Undergraduate
Department of Physics
Indian Institute of Technology
Bombay

[Dirkjan Ochtman]

On Sat, Dec 26, 2009 at 10:50, Rohit Garg <rpg...@gmail.com> wrote:
> I'd vote for git.

I'd vote for Mercurial, especially since LLVM-py is already hosted at
Google Code.

I'm happy to convert the current repository using the excellent
hgsubversion tool, if that's a problem.

Cheers,

Dirkjan

[Baptiste Lepilleur]

The code changes are actually compatible with python 2.6 & 3.1 (used #if in a few places in the patch): you can use the patched code base to install llvm-py on either python 2.6 or 3.1. For python 3.1 you also need to run 2to3 before install, but that it.

The changes are fairly small and it should be simple to backport/adapt to an earlier version.

Though, I'm sceptical w.r.t. the ability (e.g. man power) to maintain llvm-py version for all major llvm version (2.7 will be added in a few months). It would seem easier to keep up with the "current" scheme and release one or more versions of llvm-py per major llvm versions.

But you may have specific reason for sticking to 2.5 that I can't fathom...

2009/12/26 Rohit Garg <rpg...@gmail.com>

[Rohit Garg]

On Sat, Dec 26, 2009 at 8:45 PM, Baptiste Lepilleur
<baptiste....@gmail.com> wrote:
> The code changes are actually compatible with python 2.6 & 3.1 (used #if in
> a few places in the patch): you can use the patched code base to install
> llvm-py on either python 2.6 or 3.1. For python 3.1 you also need to run
> 2to3 before install, but that it.
>
> The changes are fairly small and it should be simple to backport/adapt to an
> earlier version.
>
> Though, I'm sceptical w.r.t. the ability (e.g. man power) to maintain
> llvm-py version for all major llvm version (2.7 will be added in a few
> months). It would seem easier to keep up with the "current" scheme and
> release one or more versions of llvm-py per major llvm versions.
>

At any rate, offering both Python versions would be more useful
instead of having a head for Py 2.6 and a patch for Py 3.x.

> But you may have specific reason for sticking to 2.5 that I can't fathom...

Fedora ships with LLVM 2.5 ATM, and I am not interested in recompiling
a lot of stuff :P

>
> 2009/12/26 Rohit Garg <rpg...@gmail.com>
>>
>> I assume it does not mess with LLVM's API's. I want to use it with r82
>> of llvm-py as I have LLVM 2.5.
>>
>> ATM, there are 4 branches,
>>
>> a) llvm 2.5 + py 2.6
>> b) llvm 2.5 + py 3.1
>> c) llvm 2.6 + py 2.6
>> d) llvm 2.6 + py 3.1
>>
>> it might be a good idea to switch to a dvcs to maintain these branches.
>>
>> I'd vote for git.
>>
>> On Sat, Dec 26, 2009 at 1:17 AM, Baptiste Lepilleur
>> <baptiste....@gmail.com> wrote:
>> > I've put the patch on the tracker:
>> > http://code.google.com/p/llvm-py/issues/detail?id=28
>> >
>> > I've tested it with python 2.6.2 and python 3.1 on Windows.
>> >
>> > Baptiste.
>
>

--