On Friday 16 May 2014 11:50:10 Richard Heck wrote:
> I don't, but I'd suggest you reissue this question with a new subject
> line, so everyone will see it.
>
> Richard
Fair enough. :-)
--
José Abílio
On Thursday 15 May 2014 21:07:28 Georg Baum wrote:
> This plan looks sensible. As far as OS X 10.7 is concerned:
> https://www.python.org/download/mac claims that you can install their binary
> packages in parallel to the system python, so if anybody really wants to use
> a current version of Ly
José Matos wrote:
> On Saturday 03 May 2014 07:27:51 Benjamin Piwowarski wrote:
>> Yes, but it would be good not to use it, in order to support OS X systems
>> more ancient than the current one - they are running python 2.5-2.6.
>>
>> benjamin
>
> python 2.7 was released on July of 2010. The nex
On Thursday 08 May 2014 12:57:43 Kornel Benko wrote:
> How works this code in python2?
> Sorry for my apparent ignorance.
>
> Kornel
Adding to that file
from __future__ import print_function
this works since python 2.6
--
José Abílio
On Wednesday 07 May 2014 08:35:01 Pavel Sanda wrote:
> :)) Seems the python devs really know what they are doing.
>
> Pavel
$ python -m this
The Zen of Python, by Tim Peters
...
Special cases aren't special enough to break the rules.
Although practicality beats purity.
...
Now is better than nev
José Matos wrote:
> The question regarding which is the minimum version of python 3 to support is
> more or less like this:
>
> * python 3.0 was the first implementation and it has some "features" that
> were later restored to behave as python 2.x
:)) Seems the python devs really know what the
On Wednesday 07 May 2014 11:23:48 Kornel Benko wrote:
> At least prints could be rewritten with
> import sys
> ...
> sys.out.write(...)
> or
> output = open(...)
> output.write()
>
> No dependencies on python2 or python3.
> Just my 2 cents.
But then it
On Monday 05 May 2014 09:54:40 Richard Heck wrote:
> If there are, at that time, cases where 2.7 is not going to be
> available, then we can package Python ourselves with the binary, as we
> already do on Windows.
>
> What's the reason to require 3.3+? (I'm not familiar with developments
> here
Hi,
Again - on OS X 10.7, this will not work. And I don’t think the scripts used in
LyX are that complex that we cannot handle them with using the future
statement; for the two first scripts I converted, the work was trivial and did
not require it.
We can maybe start by not using it and discu
José Matos wrote:
> On Friday 02 May 2014 13:31:36 Neal Becker wrote:
>> I think the python-future package is helpful
>
> Do you mean
>
> from __future__ import print_function, division
>
> if so I agree. :-)
>
No, I mean:
https://pypi.python.org/pypi/future
On Saturday 03 May 2014 07:27:51 Benjamin Piwowarski wrote:
> Yes, but it would be good not to use it, in order to support OS X systems
> more ancient than the current one - they are running python 2.5-2.6.
>
> benjamin
python 2.7 was released on July of 2010. The next version of lyx will be
a
On 2 May 2014 at 19:41:52 , José Matos (jama...@lyx.org) wrote:
On Friday 02 May 2014 13:31:36 Neal Becker wrote:
> I think the python-future package is helpful
Do you mean
from __future__ import print_function, division
if so I agree. :-)
Yes, but it would be good not to use it, in o
On Friday 02 May 2014 13:31:36 Neal Becker wrote:
> I think the python-future package is helpful
Do you mean
from __future__ import print_function, division
if so I agree. :-)
--
José Abílio
On 1 May 2014 at 23:06:16 , José Matos (jama...@lyx.org) wrote:
On Thursday 24 April 2014 17:13:43 Josh Hieronymus wrote:
> The question:... Was there a reason that we were using
> binary mode in the first place?
>
> Josh
IIRC it was to deal with the end line char in windows, but this wa
On Thursday 24 April 2014 17:13:43 Josh Hieronymus wrote:
> The question:... Was there a reason that we were using
> binary mode in the first place?
>
> Josh
IIRC it was to deal with the end line char in windows, but this was to support
python 2.2 and my memory is fuzzy about further details. Th
15 matches
Mail list logo
