Hello,
I'm one of the active people in #python that some people dislike for
behavior with respect to Python 3.
First of all I'd like to defuse the situation, much like Jacob.
Seriously. It's been a bunch of posts so far and most of them have
been pretty angry. Let's take a deep breath and try t
Michael,
Fair point! It's mostly put in the topic so people can ask about it
and we can give them more detailed answers, because, as other people
have mentioned, the exact answer depends largely on what *precisely*
someone is doing.
I'm not sure what sort of an effect it would have if we took it
On Sun, Jun 20, 2010 at 2:30 PM, Nick Coghlan wrote:
> On Sun, Jun 20, 2010 at 9:33 PM, Laurens Van Houtven
> wrote:
> Given the number of other links that are already in the status
> message, it would be really nice if the comment could be updated to
> something like:
>
>
On Sun, Jun 20, 2010 at 2:51 PM, Antoine Pitrou wrote:
> On Sun, 20 Jun 2010 13:33:35 +0200
> Laurens Van Houtven wrote:
> Perhaps lower the tone a bit on http://pound-python.org/ ?
> “foremost support system for developing quality Python
> applications” ... “crack team of
On Sun, Jun 20, 2010 at 3:08 PM, Nick Efford wrote:
> Thanks for explaining your position on this so carefully,
> Laurens. You've made many reasonable points which I hope will
> help to cool things down a little.
Cool, glad it's appreciated.
> Clearly, there are situations where it makes sense
On Sun, Jun 20, 2010 at 5:37 PM, Steve Holden wrote:
> Glyph Lefkowitz wrote:
>> On Jun 19, 2010, at 5:02 PM, Terry Reedy wrote:
> Which is yet another reason I don't think it would be productive to
> attempt any kind of pre-emptive action against the #python team. They do
> serve a very useful pu
Status update:
Topic now says:
NO LOL | Don't paste in here: use http://paste.pocoo.org/ |
http://pound-python.org/ | Include Python version in questions | 2.x or 3.x?
http://tinyurl.com/py2or3 | Tutorial: http://docs.python.org/tut/ | FAQ:
http://effbot.org/pyfaq/ | New Programmer? Read
http://t
On Sun, Jun 20, 2010 at 7:30 PM, Stephen J. Turnbull wrote:
> Antoine Pitrou writes:
> But we have a PR problem *now*. The loyal opposition clearly intend
> to continue trash-talking Python 3 until the libraries get to 100% (or
> a government-approved approximation of 100%). The topic on #python
On Sun, Jun 20, 2010 at 7:48 PM, Stephen J. Turnbull
wrote:
> Laurens Van Houtven writes:
>
> > Also, I'm pretty sure nobody has ever said that Python 3.x was a
> > "failure", or anything like it. #python has claims that Python 3.x, as
> > a platform for
> If there is such a disconnect we should think about remedying it: a
> large "Python 2 or 3?" button could link to a reasoned discussion of the
> pros and cons as evinced in this thread. That way people will end up
> with the right version more often (and be writing Python 2 that will
> more easil
On Sun, Jun 20, 2010 at 7:42 PM, Stephen J. Turnbull wrote:
> Laurens Van Houtven writes:
> > Yeah, I think the reason for that rule is that the majority of people
> > asking about new software actually start or end up in this category.
>
> I think that the most experienced
On Sun, Jun 20, 2010 at 9:10 PM, "Martin v. Löwis" wrote:
> Am 20.06.2010 19:48, schrieb Stephen J. Turnbull:
>> How about "Python 3 is a work in progress" for the topic?
>
> I wouldn't say that, either - not more than Python 2 was a work in progress
> over the last 10 years.
>
> Regards,
> Martin
Glad to hear the efforts are so appreciated. Unfortunately not
everyone agrees, but I'm beginning to think that's the tragedy of
internet politics :)
On Sun, Jun 20, 2010 at 10:34 PM, Terry Reedy wrote:
> On 6/20/2010 6:35 AM, Laurens Van Houtven wrote:
> I have no idea what has
That's not actually up just yet, I'd like people to review it,
personally I think it's still a tad bit biased towards Py3k. Until
then I'm keeping the Py3.x document by Nick Efford up there.
Thanks for your continued participation and seemingly endless patience,
Laurens
___
On Sun, Jun 20, 2010 at 11:30 PM, Terry Reedy wrote:
> On 6/20/2010 8:26 AM, Giampaolo Rodolà wrote:
>
>> I attempted to port pyftpdlib to python 3 several times and the
>> biggest show stopper has always been the bytes / string difference
>> introduced by Python 3 which forces you to *know* and *
Okay cool, we fixed it: http://python-commandments.org/python3.html
People are otherwise happy with the text?
Thanks for your continued input,
Laurens
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
U
On Mon, Jun 21, 2010 at 3:37 PM, Arc Riley wrote:
> I would suggest that if packages that do not have Python 3 support yet are
> listed, then their alternatives should also.
Okay, this is being worked on.
> PyQt has had Py3 support for some time.
Added, as well as PySide.
> PostgreSQL and SQLi
On Mon, Jun 21, 2010 at 5:28 PM, Toshio Kuratomi wrote:
> Fedora 14 is about the same. A nice to have thing that goes along
> with these would be a table that has packages ported to python3 and which
> distributions have the python3 version of the package.
Yeah, this is exactly why I'd prefer t
On Mon, Jun 21, 2010 at 11:03 PM, Lennart Regebro wrote:
> On Sun, Jun 20, 2010 at 18:20, Laurens Van Houtven wrote:
>> 2.x or 3.x? http://tinyurl.com/py2or3
>
> Wow. That's almost not an improvement... That link doesn't really help
> anyone choose at all.
>
>
On Tue, Jun 22, 2010 at 2:40 PM, Fred Drake wrote:
> On Tue, Jun 22, 2010 at 2:21 AM, Raymond Hettinger
> wrote:
>> I had thought there was a conscious decision to not change any existing
>> classes from old-style to new-style.
>
> I thought so as well. Changing any class from old-style to new-s
On Fri, Jun 25, 2010 at 5:34 AM, Nick Coghlan wrote:
> On Fri, Jun 25, 2010 at 11:18 AM, Terry Reedy wrote:
>> I believe there is material on the wiki as well as the two existing pages on
>> other sites that were discussed here. So a new page on python.org could
>> consist of a few links. Someone
Of course I concur with the two posters above me, but in order to
advertise for my own shop... If you're stuck with a lot of newbie
questions like these you might want to try #python (the IRC channel on
irc.freenode.net). You're more likely to get quick successive
responses there than on other medi
On Mon, Jul 26, 2010 at 12:00 PM, Michael Foord
wrote:
> At Resolver Systems we created a "calculation system" that does large
> calculations on background threads using IronPython. Doing them on a
> background thread allows the ui to remain responsive. Several calculations
> could run simultaneou
FWIW: I think Mark is right. I never quite understood why that was, but
never cared enough to complain.
lvh
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/
Hi!
This mailing list is about developing Python itself, not about developing
*in* Python or debugging Python installations.
Try seeing help elsewhere, such as on the comp.lang.python newsgroup,
#python IRC channel on freenode, or other sources (check the wiki if you
need any others).
Thanks,
l
Hi,
On using code review tools: +1, no discussion.
I've recently been doing a bit of research on these as a side effect of
researching continuous deployment, so:
1. Barry is right about Launchpad's merge proposals (unsurprisingly)
2. hg has a review extension called hg-review, but I think it'll
On Thu, Nov 4, 2010 at 5:44 AM, Allan McRae wrote:
> According to #python, we are all idiots
I realize this is not really what your message was about and for sake
of brevity you used a bit of a hyperbole, but like Thomas I would
still like to nip in right there. #python is a pretty big channe
On Fri, Nov 5, 2010 at 6:10 PM, geremy condra wrote:
> On Thu, Nov 4, 2010 at 3:40 PM, Laurens Van Houtven wrote:
>> On Thu, Nov 4, 2010 at 5:44 AM, Allan McRae wrote:
>
>
>
>> What is true is that there's a new and temporary "NO ARCH" rule in the
>&g
Whoops, pressed send too soon. This should've followed my previous email:
Unscientifically judging by the rate of people who used to have vague
problems that turned out to be Arch-related, I don't really think
anyone feels they're being told to "get lost". People ask a question
about it, which is
I'm sorry you feel that way.
Experience teaches us that people do speak up more than they tend to
keep schtum. We do get feedback on most things, including the "NO
ARCH" rule. At least so far, responses have not been anywhere near
what you'd expect if you'd tell people to "RTFM n00b" (in terms of
+1 for throwing it out of the PEP. Assignment is a thing,
nonlocal/global is a thing, don't mix them up :) (That in addition to
the grammar cleanliness argument Stephan already made)
cheers
lvh.
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
On Sat, Dec 18, 2010 at 1:12 PM, Georg Brandl wrote:
> Am 17.12.2010 17:52, schrieb Laurens Van Houtven:
>> +1 for throwing it out of the PEP. Assignment is a thing,
>> nonlocal/global is a thing, don't mix them up :) (That in addition to
>> the grammar cleanliness arg
On Thu, Dec 23, 2010 at 9:51 PM, Georg Brandl wrote:
> Yes and no -- there may not be an ambiguity to the parser, but still to
> the human. Except if you disallow the syntax in any case, requiring
> people to write
>
> nonlocal x = (3, y)
>
> which is then again inconsistent with ordinary assignm
On Thu, Mar 24, 2011 at 12:18 AM, Thomas Wouters wrote:
> It ended up that Jim Fulton is actually writing the PEP (with input from
> Twisted people and others.)
>
> --
> Thomas Wouters
>
> Hi! I'm a .signature virus! copy me into your .signature file to help me
> spread!
>
>
Well, if help is sti
On Thu, Apr 28, 2011 at 9:51 PM, Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
> Personally, I think the status quo is fine
> and that practicality is beating purity.
>
+1
>
> Raymond
>
cheers
lvh
___
Python-Dev mailing list
Python-Dev@pyth
Hi!
This list is for developing Python itself, not about developing *in* Python.
For more support try the comp.lang.python newsgroup or the equivalent
http://mail.python.org/mailman/listinfo/python-list mailing list, or the
#python IRC channel on Freenode.
cheers
lvh
On Mon, Jul 18, 2011 at 5:32
On Tue, Aug 23, 2011 at 8:46 PM, Barry Warsaw wrote:
> On Aug 23, 2011, at 08:39 PM, Ross Lagerwall wrote:
>
> >> When reviewing the PEP 3151 implementation (*), Ezio commented that
> >> "FileSystemError" looks a bit strange and that "FilesystemError" would
> >> be a better spelling. What is your
Sure, you just *do* it. The only advantage I see in assertNotRaises is that
when that exception is raised, you should (and would) get a failure, not an
error.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
Oops, I accidentally hit Reply instead of Reply to All...
On Wed, Sep 28, 2011 at 1:05 PM, Michael Foord wrote:
> On 27/09/2011 19:59, Laurens Van Houtven wrote:
>
> Sure, you just *do* it. The only advantage I see in assertNotRaises is that
> when that exception is raised, you
Hello :)
That PEP is indeed pining to the fjords. I may be able to contribute (and
hopefully I can with the preliminary research and
talking-to-people-about-what-they-want that I've already done that maybe
hasn't made it into the draft PEP versions), but I can not currently spare
the cycles to car
Looks reasonable to me :) Comments:
create_transport "combines" a transport and a protocol. Is that process
reversible? that might seem like an exotic thing (and I guess it kind of
is), but I've wanted this e.g for websockets, and I guess there's a few
other cases where it could be useful :)
eof_
41 matches
Mail list logo
