Really please, please don't top post.
http://www.river.com/users/share/etiquette/
Who cares! it takes too long to scroll down through the past fifteen
generations to get to the relevant part of the message.
Well, it takes me one keystroke. Get a better mail client.
Whenever I try
Hey Jeff,
Interesting points.
On Wednesday 08 December 2010 08:48:07 Jeff Cook wrote:
Whenever I try bottom-posting, my clients complain that I just sent
them a blank email.
I think the trick is not to top or bottom post, but to interleave your reply,
keeping the relevant parts of the
On Wed, 2010-12-08 at 01:48 -0700, Jeff Cook wrote:
Really please, please don't top post.
http://www.river.com/users/share/etiquette/
Who cares! it takes too long to scroll down through the past fifteen
generations to get to the relevant part of the message.
Well, it takes me one
Scroll CLEAR down to the bottom for my response.
On Wed, Oct 20, 2010 at 12:02:27PM -0400, Matthew Gyurgyik wrote:
On 10/20/2010 11:45 AM, maxc wrote:
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
Guido seems to
Den 06. des. 2010 18:27, skrev Steve Holmes:
Really please, please don't top post.
http://www.river.com/users/share/etiquette/
Who cares! it takes too long to scroll down through the past fifteen
generations to get to the relevant part of the message.
That no problem as you only keep the
On Mon, Dec 6, 2010 at 11:48 AM, Christoffer Hirth li...@toffyrn.net wrote:
Den 06. des. 2010 18:27, skrev Steve Holmes:
Really please, please don't top post.
http://www.river.com/users/share/etiquette/
Who cares! it takes too long to scroll down through the past fifteen
generations to
On Mon, 2010-12-06 at 10:27 -0700, Steve Holmes wrote:
Really please, please don't top post.
http://www.river.com/users/share/etiquette/
Who cares! it takes too long to scroll down through the past fifteen
generations to get to the relevant part of the message.
If you're posting on an ML
On Mon 06 Dec 2010 10:27 -0700, Steve Holmes wrote:
Scroll CLEAR down to the bottom for my response.
On Wed, Oct 20, 2010 at 12:02:27PM -0400, Matthew Gyurgyik wrote:
Really please, please don't top post.
http://www.river.com/users/share/etiquette/
Who cares! it takes too long to scroll
is a simple fact of relinking to python2 or there can be problems of
libraries ?
for example, reportlab does work ?
thanks
You know what you could do is something like
rm /usr/bin/python
echo /usr/bin/python HERE
#! /bin/bash
[ -z $_PYTHON ] _PYTHON=/usr/bin/python2
$_PYTHON $@
HERE
chmod 755 /usr/bin/python
if the transition is bothering you too much. Then when things calm down a
little you just delete that
Hi,
I don't agree that python 3 is ready for mass use yet. I think arch
made a premature switch.
Hence, I am not upgrading my system. I hope archlinux rollbacks python3 update.
Regards,
Gary
That won't happen! And I hope you know that python2 isn't gone, it's still
available. All the package maintainers have to do is change the sheband. Of
course that needs a little bit of work, but that's really not the biggest deal!
If there are AUR packages which haven't done these changes yet,
* Gaurish Sharma cont...@gaurishsharma.com [22.10.2010 19:21]:
Hi,
I don't agree that python 3 is ready for mass use yet. I think arch
made a premature switch.
Hence, I am not upgrading my system. I hope archlinux rollbacks python3
update.
Regards,
Gary
I just installed the
On Fri, 2010-10-22 at 22:50 +0530, Gaurish Sharma wrote:
Hi,
I don't agree that python 3 is ready for mass use yet. I think arch
made a premature switch.
Hence, I am not upgrading my system. I hope archlinux rollbacks python3
update.
Regards,
Gary
Hey look, devs did something I didn't
Just a little story that is relevant to this discussion
I ran into a problem with python and proprietary software earlier today, but
was able (through much tribulaton) to work around it. Even after most open-
source code is using python 3, a lot of proprietary stuff may still depend on
Em 20-10-2010 13:21, Daenyth Blank escreveu:
On Wed, Oct 20, 2010 at 11:16, Armando M. Baratti
ambaratti.lis...@gmail.com wrote:
Em 20-10-2010 05:24, Stefano Z. escreveu:
anyone know if reportlab does work with python3 ?
No, reportlab doesn't work with python3.
Neither Django, nor
On Thu, Oct 21, 2010 at 3:45 PM, Armando M. Baratti
ambaratti.lis...@gmail.com wrote:
Yes, off course I do. But I also realize that, besides Python isn't the
easiest platform to deploy to, specially when your customers aren't tech
savvy and have to make some adjustment or install some
anyone know if reportlab does work with python3 ?
Max Countryman maxc at me.com writes:
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
Oh is there another thread on this list? My apologies if so! I just joined
earlier yesterday. :)
On Oct 20, 2010, at 12:31 AM, Mithrandir wrote:
Ha ha! We posted at virtually the same time! (Or not...) :D
On Wed, 20 Oct 2010 04:31:17 + (UTC)
Mithrandir mithrandirag...@lavabit.com wrote:
Max Countryman maxc at me.com writes:
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
I think that my only concern at this point is how the Python development team
sees the future of the binary: if the python and python3 convention is kept I
worry about the ease of portability apropos to development under Arch.
For further in-depth discussion of the overall move the comments of
On Wed, Oct 20, 2010 at 8:52 AM, Hilton Medeiros
medeiros.hil...@gmail.com wrote:
On Wed, 20 Oct 2010 04:31:17 + (UTC)
Mithrandir mithrandirag...@lavabit.com wrote:
Max Countryman maxc at me.com writes:
I failed to find a reference, but I seem to remember the Python
team
deciding
On Wed, Oct 20, 2010 at 9:03 AM, C Anthony Risinger anth...@extof.me wrote:
i like the python2.7, python2, python3.1, python3, etc, scheme... i
think this makes it very easy for developers to select the specific
interpreter they need, if any. i hope this trend becomes/is defacto.
if you are
On Wed, Oct 20, 2010 at 9:14 AM, Max Countryman m...@me.com wrote:
But is that what Python development has decided?
I'm not sure what they have recommended. Ultimately it's up to the
distros to decide such things; I have seen that written more then once
by BFDL and friends.
I think what Arch
That is fine unless the Python development team has decide that python3 will
not become python.
Python 2.7.x will be maintained for quite some time. (In excess of four more
years.) Even after it is dropped in the future there's no indication that the
python3 binary is intended to become the
On 10/20/2010 10:58 AM, Max Countryman wrote:
That is fine unless the Python development team has decide that python3 will
not become python.
Python 2.7.x will be maintained for quite some time. (In excess of four more
years.) Even after it is dropped in the future there's no indication that
Em 20-10-2010 05:24, Stefano Z. escreveu:
anyone know if reportlab does work with python3 ?
No, reportlab doesn't work with python3.
Neither Django, nor Twisted.
As well the modules below are incompatible with python3 (to mention a few):
- PyGTK2
- Pyjamas
- Kiwi
- Beaker
- Cheetah
-
On Wed, Oct 20, 2010 at 11:16, Armando M. Baratti
ambaratti.lis...@gmail.com wrote:
Em 20-10-2010 05:24, Stefano Z. escreveu:
anyone know if reportlab does work with python3 ?
No, reportlab doesn't work with python3.
Neither Django, nor Twisted.
As well the modules below are incompatible
On Wed, 20 Oct 2010 10:58:42 -0400
Max Countryman m...@me.com wrote:
That is fine unless the Python development team has decide that
python3 will not become python.
Python 2.7.x will be maintained for quite some time. (In excess of
four more years.) Even after it is dropped in the future
On 10/20/2010 11:45 AM, maxc wrote:
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
Guido seems to favor using /usr/bin/python3.0 or /usr/bin/python3 and
/usr/bin/python as symlinks to the respective versions of Python.
On Wed, Oct 20, 2010 at 11:02 AM, Matthew Gyurgyik pyt...@pyther.net wrote:
On 10/20/2010 11:45 AM, maxc wrote:
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
Guido seems to favor using /usr/bin/python3.0 or
Am Wed, 20 Oct 2010 12:02:27 -0400
schrieb Matthew Gyurgyik pyt...@pyther.net:
Really please, please don't top post.
http://www.river.com/users/share/etiquette/
And, really please, only quote the relevant parts to which the answer
refers.
Heiko
On 11:17 Wed 20 Oct , Dan McGee wrote:
Fucking hell! Can we stop with this constant nagging on the list? It
doesn't help (as you can see), you waste 1926 people's time with the
message (yes, this list has this many subscribers, and it is soon to
be one less), and it just doesn't need to be
On Wed, Oct 20, 2010 at 10:45 AM, maxc m...@me.com wrote:
There is an excellent post by Guido here, Hilton:
http://mail.python.org/pipermail/python-3000/2008-February/011910.html
Guido seems to favor using /usr/bin/python3.0 or /usr/bin/python3 and
/usr/bin/python as symlinks to the
On Wed, Oct 20, 2010 at 12:10:03PM -0500, C Anthony Risinger wrote:
the point is that it really, really, really... doesn't matter what
`python` is symlinked to. developers need to have the competence to
instruct the system appropriately, and construct the environment they
need to function
On Wed, Oct 20, 2010 at 3:00 PM, f...@kokkinizita.net wrote:
On Wed, Oct 20, 2010 at 12:10:03PM -0500, C Anthony Risinger wrote:
the point is that it really, really, really... doesn't matter what
`python` is symlinked to. developers need to have the competence to
instruct the system
On 10/20/2010 06:52 AM, Hilton Medeiros wrote:
HackerNews, Slashdot, ...:
- Someone post an announcement with 10 lines;
- They read it (or not) and think that that is all the information
behind the story;
- They furiously start typing the first thing that pops in their mind;
Often preceded
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 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]
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 make life
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 the
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 need
On Tue, Oct 19, 2010 at 20:36, Max Countryman m...@me.com 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
On Tue, Oct 19, 2010 at 7:25 PM, Max Countryman m...@me.com 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
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
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 with
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
48 matches
Mail list logo
