On 1/9/07, Aahz <[EMAIL PROTECTED]> wrote:
Hey! What's this about __cmp__?!
Python 3.0x (p3yk:53295, Jan 8 2007, 09:32:17)
[GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
object.__cmp__
Traceback (most re
On 1/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> FWIW, I wasn't aware that things like "except T, (a, b, c):" were
> possible until I started work on this patch; I thought was all
> you _could_ use.
And, given the secial semantics for this position, I would support
changing the syntax to *on
> > On 12/30/06, Talin <[EMAIL PROTECTED]> wrote:
> > > Maybe this would be a good time to review, or at least restate, the
> > > specific plans for strings in Py3K? I know that there's been a great
> > > deal of discussion on this, but a lot of that discussion took place
> > > *before* Larry's wor
On 1/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> And, given the secial semantics for this position, I would support
> changing the syntax to *only* allow a single simple name there -- not
> even x.y.z. Thsh should handle 99.9% of existing code anyway.
>
> (And yes, if someone wants to add t
Guido van Rossum wrote:
> On 1/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
>> FWIW, I wasn't aware that things like "except T, (a, b, c):" were
>> possible until I started work on this patch; I thought was all
>> you _could_ use.
>
> And, given the secial semantics for this position, I would s
At 08:10 AM 1/10/2007 +1100, Tim Delaney wrote:
>Guido van Rossum wrote:
>
> > On 1/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> >> FWIW, I wasn't aware that things like "except T, (a, b, c):" were
> >> possible until I started work on this patch; I thought was all
> >> you _could_ use.
> >
>
Since the threads on what modules to remove has puttered out (which I
take it to mean people no longer are having any fits over the list
which makes me happy =), I figured we can move on to the open issue of
new packages. Lots of people seem to pick up on it when I posted the
full PEP so I am hopi
On 1/9/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> That seems fine for 2.x, but 3.x should have Only One Way To Do It. 2.x
> needs both syntaxes to support writing forward-compatible code.
Really? I personally expect that that's a lost cause. A much more
modest goal would be to write code tha
On 1/5/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Obsolete
>
>
> Becoming obsolete signifies that either another module in the stdlib
> or a widely distributed third-party library provides a better solution
> for what the module is meant for.
How about the sets module? The set and froz
On 1/9/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 1/5/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > Obsolete
> >
> >
> > Becoming obsolete signifies that either another module in the stdlib
> > or a widely distributed third-party library provides a better solution
> > for what the
On Tuesday 09 January 2007 17:27, Brett Cannon wrote:
> - syslog
There's nothing Unix-specific about syslog (other than history), but the
syslog module itself is Unix-specific. Given that there's a Python
implementation of a syslog client in the logging module, would it make sense
to refa
On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> * 'collections' package
>
> + heapq
> + Queue
Putting this in a collections package might exacerbate the confusion
over its intended use. It really is more of a threading
synchronization tool than a general queue datastructure (though it
On 1/9/07, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
> On Tuesday 09 January 2007 17:27, Brett Cannon wrote:
> > - syslog
>
> There's nothing Unix-specific about syslog (other than history), but the
> syslog module itself is Unix-specific. Given that there's a Python
> implementation of a sys
On 1/9/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> >
> > * 'collections' package
> >
> > + heapq
> > + Queue
>
> Putting this in a collections package might exacerbate the confusion
> over its intended use. It really is more of a threading
>
On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 1/9/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> > Does the sets module serve any purpose other than backward
> > compatibility? Why not remove those module for py3k?
>
> Same reason that the User* modules still exist I suppose. Plus I
> don'
On 1/9/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > On 1/9/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> > > Does the sets module serve any purpose other than backward
> > > compatibility? Why not remove those module for py3k?
> >
> > Same rea
On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> * Profiling
>
> + cProfile
> + profile
> + hotshot
> + pstats
Perhaps 'diagnostics' instead, with pdb thrown in? Hopefully there
will be more tools in the future.
--
Adam Olsen, aka Rhamphoryncus
__
On 1/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 1/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> > FWIW, I wasn't aware that things like "except T, (a, b, c):" were
> > possible until I started work on this patch; I thought was all
> > you _could_ use.
>
> And, given the secial seman
OK, let me repeat myself.
I see no point in grouping modules just because they're servers.
I'd suggest a Web module containing:
html:
htmlentitydefs
htmllib
HTMLParser
sgmllib (?)
server:
BaseHTTPServer
cgi
CGIHTTPServer
Cookie
wsgiref
client:
co
On 1/9/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> OK, let me repeat myself.
>
OK.
> I see no point in grouping modules just because they're servers.
>
That's fine. But they do server a similar purpose and so it is a
legit suggestion. If no one else likes it then it won't go anywhere.
I wil
On 1/9/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 1/9/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > On 1/9/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> > > Does the sets module serve any purpose other than backward
> > > compatibility? Why not remove those module for py3k?
> >
> > Same rea
cc'ing python-dev - followups should probably go there, rather than
the p3yk list.
So here's my latest plan:
- Add a Py3KDeprecationWarning, as a subclass of DeprecationWarning
(or maybe just of Warning)
- Add a -W py3k shortcut, which is the same as
"-W once:Py3kDeprecationWarning"
- Add a C
In the p3yk branch, test_hotshot seems to be failing. Does anybody
have any idea why? Is this an artefact of the latest merge? (BTW
thanks for doing another merge, Thomas -- it's greatly appreciated!)
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
"Brett Cannon" <[EMAIL PROTECTED]> wrote:
> * Databases
> + anydbm
> + dbhash
> + dbm
> + bsddb
> + dumbdbm
> + gdbm
> + whichdb
What about sqlite3?
> * Internet (leaving out all questionable modules leads to a Web
> grouping)
I'm not a real big fan of the Internet package, but
"Collin Winter" <[EMAIL PROTECTED]> wrote:
> On 1/9/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 1/8/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> > > FWIW, I wasn't aware that things like "except T, (a, b, c):" were
> > > possible until I started work on this patch; I thought was all
On Wednesday 10 January 2007 16:31, Guido van Rossum wrote:
> In the p3yk branch, test_hotshot seems to be failing. Does
> anybody have any idea why? Is this an artefact of the latest
> merge? (BTW thanks for doing another merge, Thomas -- it's
> greatly appreciated!)
It works fine for me...
On Tue, Jan 09, 2007 at 06:18:21PM -0800, Bill Janssen wrote:
> server:
> Cookie
>
> client:
> cookielib
server:
cookie
client:
cookie
?
Oleg.
--
Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED]
Programmers don't die, they just GOSU
27 matches
Mail list logo
