Displaying 3 results from an estimated 3 matches for "python3port".
2012 Dec 04
0
[LLVMdev] Minimum Python Version
...moved in python3 and I saw in
a couple places.
The bottom line is that basically every guide to
porting/interoperating with python3 starts with "step 1: use python
2.6 at least, ideally 2.7". Given the need to interoperate with py3k,
the need to get to 2.6 at least is compelling.
http://python3porting.com/preparing.html ("The first step in the
porting process is to get your code running in Python 2.6 or 2.7.")
https://wiki.ubuntu.com/Python/3 ("Target Python 3.2, 2.7, and
optionally 2.6. Ignore anything older than that.")
http://lucumr.pocoo.org/2011/1/22/forwards-compatib...
2012 Dec 04
2
[LLVMdev] Minimum Python Version
On 12/04/2012 12:28 AM, Sean Silva wrote:
> On Mon, Dec 3, 2012 at 6:56 AM, Tobias Grosser<tobias at grosser.es> wrote:
>> The gcc compile farm currently only has python 2.4 and 2.5. I know Duncan is
>> using it quiet extensively, especially all dragonegg buildbots run on it.
>>
>> I very much agree we should ensure our python scripts are valid python 2.7
>>
2012 Dec 04
5
[LLVMdev] Minimum Python Version
...uot;step 1: use python
> 2.6 at least, ideally 2.7". Given the need to interoperate with py3k,
> the need to get to 2.6 at least is compelling.
Our code is fully 2.7 compatible. They ask for that compatibility, not
to introduce features that only work in 2.7 but not in 2.4.
> http://python3porting.com/preparing.html ("The first step in the
> porting process is to get your code running in Python 2.6 or 2.7.")
> https://wiki.ubuntu.com/Python/3 ("Target Python 3.2, 2.7, and
> optionally 2.6. Ignore anything older than that.")
> http://lucumr.pocoo.org/2011/1/...