>> Hmm... I probably should have added a version to the provides line in the
>> python package. Currently it only provides "python3" and not a version so
>> the versioned deps in those AUR packages are causing issues. I'll get
>> around to that before this exits [testing]
>
> Um... did you
Apologies, link cut in original quote:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
On Oct 19, 2010, at 9:58 PM, Max Countryman wrote:
>> I failed to find a reference, but I seem to remember the Python team
>> deciding at some point that they intended to keep the name
> I failed to find a reference, but I seem to remember the Python team deciding
> at some point that they intended to keep the name "python" for the Python 2.X
> binaries perpetually, and require Python 3.X to be invoked as "python3". Arch
> might be alone in making this change, and inconsistent
On 20/10/10 10:25, Max Countryman wrote:
First, thank you for the link, it's good to read a more fleshed out perspective.
Of course, your own python scripts will need to point at /usr/bin/python2.
However, by doing this you may run into portability issues across distros.
There does not appear
On Tue, Oct 19, 2010 at 7:25 PM, Max Countryman wrote:
> First, thank you for the link, it's good to read a more fleshed out
> perspective.
>
>> Of course, your own python scripts will need to point at /usr/bin/python2.
>> However, by doing this you may run into portability issues across distros
On Tue, Oct 19, 2010 at 20:36, Max Countryman wrote:
>
>> It seems that while most (all?) distributions include a /usr/bin/python3
>> link to their python3.xbinary, none do the same thing for python2.x. Either
>> create your own symlink in your path for those distros or even better file a
>> bu
> It seems that while most (all?) distributions include a /usr/bin/python3 link
> to their python3.xbinary, none do the same thing for python2.x. Either create
> your own symlink in your path for those distros or even better file a bug
> with them asking for such a symlink. They are going to ne
First, thank you for the link, it's good to read a more fleshed out perspective.
> Of course, your own python scripts will need to point at /usr/bin/python2.
> However, by doing this you may run into portability issues across distros.
> There does not appear to be an easy solution for that at th
Andrea Scarpino [2010.10.20 0201 +0200]:
> On Wednesday 20 October 2010 01:47:20 Max Countryman wrote:
> > I'm curious what the rationale is behind changing the default to Python 3?
> >
> > My understanding is that many libraries are not yet available on Python 3.
> > As a developer, this could ma
On Tue, Oct 19, 2010 at 6:37 PM, Ray Rashif wrote:
> On 20 October 2010 07:25, Norbert Zeh wrote:
>> Hi folks,
>>
>> With the python upgrade from 2.7 to 3.1, I ran into the following snag.
>> gitosis from AUR depends on python and setuptools. Now, python =
>> python3.1 now and setuptools install
On Wednesday 20 October 2010 01:47:20 Max Countryman wrote:
> I'm curious what the rationale is behind changing the default to Python 3?
>
> My understanding is that many libraries are not yet available on Python 3.
> As a developer, this could make life difficult.
You should read Allan's post[1]
I'm curious what the rationale is behind changing the default to Python 3?
My understanding is that many libraries are not yet available on Python 3. As a
developer, this could make life difficult.
Regards,
Max Countryman
On 20 October 2010 07:25, Norbert Zeh wrote:
> Hi folks,
>
> With the python upgrade from 2.7 to 3.1, I ran into the following snag.
> gitosis from AUR depends on python and setuptools. Now, python =
> python3.1 now and setuptools installs in the python2.7 library tree.
> This was easy enough to
Hi folks,
With the python upgrade from 2.7 to 3.1, I ran into the following snag.
gitosis from AUR depends on python and setuptools. Now, python =
python3.1 now and setuptools installs in the python2.7 library tree.
This was easy enough to fix, by simply replacing python with python2 in
the gitos
On 10/18/2010 09:50 PM, Allan McRae wrote:
> On 19/10/10 12:43, David C. Rankin wrote:
>> Here is a new one for me
>>
>> A system update tonight provided the following note:
>>
>> ==> NOT included depencies(with reasons):
>> - sidplay - we do not have sidplay 2 series in repos; also it's
>>
On 10/19/10 10:35, Dan McGee wrote:
On Tue, Oct 19, 2010 at 9:20 AM, Jan Steffens wrote:
On Tue, Oct 19, 2010 at 2:39 PM, Dan McGee wrote:
Community feedback welcome as well, but this is now in testing now
that the Python rebuild has moved on. Please let me know (good and
bad) how things are
El 19/10/10 07:13, Heiko Baums dijo:
> Am Tue, 19 Oct 2010 18:54:16 +0200
> schrieb Clément Démoulins :
>
> > Le 19/10/2010 16:50, Fess a écrit :
> > > I think this is useful information: all soft installed from aur
> > > need to be reinstalled with changing line like "python setup.py
> > > blah-b
Am Tue, 19 Oct 2010 18:54:16 +0200
schrieb Clément Démoulins :
> Le 19/10/2010 16:50, Fess a écrit :
> > I think this is useful information: all soft installed from aur
> > need to be reinstalled with changing line like "python setup.py
> > blah-blah" to line "python2 setup.py blah-blah". Because
2010/10/19 Clément Démoulins :
> Le 19/10/2010 16:50, Fess a écrit :
>> I think this is useful information: all soft installed from aur need to be
>> reinstalled with changing line like "python setup.py blah-blah" to line
>> "python2 setup.py blah-blah". Because some packages still aren't
>> tou
Le 19/10/2010 16:50, Fess a écrit :
> I think this is useful information: all soft installed from aur need to be
> reinstalled with changing line like "python setup.py blah-blah" to line
> "python2 setup.py blah-blah". Because some packages still aren't touched(e.g.
> charm).
> So, something lik
I think this is useful information: all soft installed from aur need to be
reinstalled with changing line like "python setup.py blah-blah" to line
"python2 setup.py blah-blah". Because some packages still aren't touched(e.g.
charm).
So, something like that.
--
On Tue, Oct 19, 2010 at 9:35 AM, Dan McGee wrote:
> On Tue, Oct 19, 2010 at 9:20 AM, Jan Steffens wrote:
>> On Tue, Oct 19, 2010 at 2:39 PM, Dan McGee wrote:
>>> Community feedback welcome as well, but this is now in testing now
>>> that the Python rebuild has moved on. Please let me know (good
On Tue, Oct 19, 2010 at 9:20 AM, Jan Steffens wrote:
> On Tue, Oct 19, 2010 at 2:39 PM, Dan McGee wrote:
>> Community feedback welcome as well, but this is now in testing now
>> that the Python rebuild has moved on. Please let me know (good and
>> bad) how things are going with it so I can move i
On Tue, Oct 19, 2010 at 4:20 PM, Jan Steffens wrote:
> On Tue, Oct 19, 2010 at 2:39 PM, Dan McGee wrote:
>> Community feedback welcome as well, but this is now in testing now
>> that the Python rebuild has moved on. Please let me know (good and
>> bad) how things are going with it so I can move i
On Tue, Oct 19, 2010 at 2:39 PM, Dan McGee wrote:
> Community feedback welcome as well, but this is now in testing now
> that the Python rebuild has moved on. Please let me know (good and
> bad) how things are going with it so I can move it along to [extra].
Lots of stuff seems to be missing from
On Tue, Oct 19, 2010 at 8:35 AM, Joe(theWordy)Philbrook wrote:
>
> It would appear that on Oct 14, Thomas Bächler did say:
>
>> My recommendations:
>> 1) If you are upgrading your desktop environment, exit your session,
>> quit your login manager and upgrade from the text console. I advise to
>> r
It would appear that on Oct 14, Thomas Bächler did say:
> My recommendations:
> 1) If you are upgrading your desktop environment, exit your session,
> quit your login manager and upgrade from the text console. I advise to
> run pacman -Sywu from the desktop and when the download finishes, run
> p
On 06:51 Tue 19 Oct , Guillermo Leira wrote:
> > After the last Pacman -Syu, I can't login with gdm. As soon as I clikc on my
> > username, the system seems to freeze... Although not completely: I can ping
> > from other computer, but I can't ssh.
> >
> > Before I click on the username, the "s
On Tue, Oct 19, 2010 at 10:56 AM, karl wrote:
> On 06:51 Tue 19 Oct , Guillermo Leira wrote:
> > > After the last Pacman -Syu, I can't login with gdm. As soon as I clikc
> on my
> > > username, the system seems to freeze... Although not completely: I can
> ping
> > > from other computer, but
On 06:51 Tue 19 Oct , Guillermo Leira wrote:
> > After the last Pacman -Syu, I can't login with gdm. As soon as I clikc on my
> > username, the system seems to freeze... Although not completely: I can ping
> > from other computer, but I can't ssh.
> >
> > Before I click on the username, the "s
30 matches
Mail list logo
