We'll see if/when that starts happening. If Python 2 is what companies use
in production, their developers will build also new packages to prioritize
python 2.
On Fri, Jan 16, 2015 at 9:03 PM, Kent Tenney wrote:
> > Anyway inevitably there will be packages not available for python3,
> (legacy)
>
> Anyway inevitably there will be packages not available for python3,
(legacy)
and newer packages will not be available for python2
(because they leverage py3 features)
On Fri, Jan 16, 2015 at 9:28 AM, 'Terry Brown' via leo-editor
wrote:
> This thread has inspired me to get things working in Py
On Fri, Jan 16, 2015 at 12:13 PM, Ville M. Vainio
wrote:
> Further thought - it's still unclear which one is the dead end, python 2
> or python 3.
>
> There is very little motivation still to prioritize python 3 when python 2
> has all the users and developers - everyone ensures their stuff works
On Fri, Jan 16, 2015 at 12:03 PM, Ville M. Vainio
wrote:
> PIP is routinely used with python 2 - in fact a lot of modules in PyPI is
> Python 2 only.
>
True. The nice feature of Python 3.4 is that pip is installed
automatically.
Edward
--
You received this message because you are subscribed
Further thought - it's still unclear which one is the dead end, python 2 or
python 3.
There is very little motivation still to prioritize python 3 when python 2
has all the users and developers - everyone ensures their stuff works on
python 2, and python 3 is "voluntary extra".
On Fri, Jan 16, 20
PIP is routinely used with python 2 - in fact a lot of modules in PyPI is
Python 2 only.
You can get it here: https://pip.pypa.io/en/latest/installing.html
On Fri, Jan 16, 2015 at 1:20 PM, Edward K. Ream wrote:
>
>
> On Wednesday, January 14, 2015 at 9:31:32 AM UTC-6, Edward K. Ream wrote:
>>
>
This thread has inspired me to get things working in Python3, i.e. Leo
plus all the plugins I use.
I have PyQt5 installed in Python3, so this includes fixing Qt4/5 stuff.
Notes so far:
paramiko is a package for Ubuntu 14.04 for 2.7 but not 3, no big deal,
pip3 can install it.
I've been loading
On Wednesday, January 14, 2015 at 9:31:32 AM UTC-6, Edward K. Ream wrote:
>
> On Wed, Jan 14, 2015 at 8:05 AM, Ville M. Vainio
> wrote:
>
>> FWIW, I'm pretty pessimistic about Python 3 at this point. Python 2 seems
>> to be "good enough" for most people.
>>
>
> I am not real optimistic about
On Wed, Jan 14, 2015 at 9:40 AM, Kent Tenney wrote:
> Oh, I didn't understand that the question was whether or
> not to abandon 2, that wouldn't be good.
>
The question is merely whether to encourage Leo's core developers to use
Python 3 when writing (and checking!) their code. Leo will contin
Oh, I didn't understand that the question was whether or
not to abandon 2, that wouldn't be good.
I'd welcome help from someone running Leo trunk in a virtualenv
with Py3 and PyQt5
On Wed, Jan 14, 2015 at 9:26 AM, Edward K. Ream wrote:
> On Tue, Jan 13, 2015 at 10:06 AM, Kent Tenney wrote:
>>
>
On Wed, Jan 14, 2015 at 8:05 AM, Ville M. Vainio wrote:
> FWIW, I'm pretty pessimistic about Python 3 at this point. Python 2 seems
> to be "good enough" for most people.
>
I am not real optimistic about Python 3 myself.
As Kent says, more and more packages are being ported. But Guido has
On Tue, Jan 13, 2015 at 10:06 AM, Kent Tenney wrote:
> I recently tried to switch to v3, as I remember, I was thwarted
> by problems having to do with PyQT in a virtualenv.
>
That may be, but I am talking about Leo's core developers, who presumably
can create a stable Python3K environment.
Oto
But the switch is happening, existing libraries are being
ported, new code is leveraging Python 3 benefits ...
On Wed, Jan 14, 2015 at 8:05 AM, Ville M. Vainio wrote:
> FWIW, I'm pretty pessimistic about Python 3 at this point. Python 2 seems to
> be "good enough" for most people.
>
> On Tue, Jan
FWIW, I'm pretty pessimistic about Python 3 at this point. Python 2 seems
to be "good enough" for most people.
On Tue, Jan 13, 2015 at 6:06 PM, Kent Tenney wrote:
> I recently tried to switch to v3, as I remember, I was thwarted
> by problems having to do with PyQT in a virtualenv.
>
> I current
I recently tried to switch to v3, as I remember, I was thwarted
by problems having to do with PyQT in a virtualenv.
I currently run Leo in a virtualenv, I think I linked to system
files to make PyQT work, but I don't remember how I did it.
So, I'd like a virtualenv with 3.x Python to run Leo from
I would like to have most (all?) Leo developers develop and test using
3.x. Would that be a problem for anyone?
Guido has stated that there will be no version 2.8 of Python:
http://legacy.python.org/dev/peps/pep-0404/ (Hahaha: Pep 404)
although some disagree:
http://blog.startifact.com/posts/the
16 matches
Mail list logo
