Le jeudi 22 juillet 2010 à 07:23 -0500, Benjamin Peterson a écrit :
> 2010/7/22 Antoine Pitrou :
> > On Thu, 22 Jul 2010 08:51:57 +0100
> > Brett Cannon wrote:
> >>
> >> That's an option. I just remember Tim bringing up something about that
> >>
On Thu, 22 Jul 2010 13:22:48 +0200
stefan brunthaler wrote:
>
> I wonder whether you would be interested in integrating these
> optimizations with the Python 3 distribution, hence this mail. I could
> send copies of the papers, as well as provide my prototype source code
> to interested members o
Hello all,
PEP 360 - “Externally Maintained Packages” seems to have outdated
contents.
First of all, I don't think Optik and wsgiref are externally
maintained anymore (both seem unmaintained by their original authors).
Second, the version numbers mentioned there could be out of date too
(especial
On Thu, 22 Jul 2010 16:54:58 +0100
Georg Brandl wrote:
>
> You raise a good point. However, I'd rather explicitly signify names instead
> of keywords:
>
> for $boo in $foo:
> if $boo is $None:
> print($hoo)
> else:
> return sorted($woo)
>
> That also has the advantage o
On Tue, 27 Jul 2010 09:57:22 +0200
Georg Brandl wrote:
> Am 27.07.2010 04:43, schrieb Terry Reedy:
> > On 7/26/2010 5:15 PM, Georg Brandl wrote:
> >
> >> Sure PyPI is part of the ecosystem. But so are quite a lot of other tools,
> >> and none of them are tracked in bugs.python.org. (This is al
On Wed, 28 Jul 2010 11:56:16 +0100
Michael Foord wrote:
> > This is the kind of approach that seems to hold the most promise of
> > removing the GIL without incurring the single-threaded performance hit
> > that has been the achilles heel of previous attempts at creating a
> > free-threaded CPytho
On Sun, 01 Aug 2010 13:01:32 +1200
Greg Ewing wrote:
> While updating my yield-from impementation for Python
> 3.1.2, I came across a quirk in the way that the new
> exception chaining feature interacts with generators.
>
> If you close() a generator, and it raises an exception
> inside a finally
On Sun, 01 Aug 2010 17:22:55 +0200
Éric Araujo wrote:
> > Speaking of which... Your documentation says it's named ~/unittest.cfg,
> > could you make this a file in the user base (that is, the prefix where
> > 'setup.py install --user' will install files)?
>
> Putting .pydistutils.cfg .pypirc .uni
On Mon, 02 Aug 2010 08:10:58 +0200
Georg Brandl wrote:
> Thanks, Benjamin! I'd also like to thank Martin and Ronald for the prompt
> binaries, and the folks of #python-dev for support. RMing was a pleasant
> experience so far.
Are you already trying to lure other people into replacing you?
__
On Mon, 2 Aug 2010 17:13:01 -0500
Benjamin Peterson wrote:
> 2010/8/2 Nick Coghlan :
> > On Tue, Aug 3, 2010 at 7:18 AM, Benjamin Peterson
> > wrote:
> >> I'm only referring to the infrastructure when I say "the current
> >> setup." I don't think repeatedly tweaking the tracker is likely to
> >
On Tue, 03 Aug 2010 00:00:46 +0100
Mark Lawrence wrote:
>
> Fly back at me if you like. I don't care about me. I don't care about
> you. I do care about Python.
Well, you should care about people. Free software is as much as about
building welcoming communities than it is about writing good
On Tue, 03 Aug 2010 10:28:07 +0200
"M.-A. Lemburg" wrote:
> >
> > Don't forget system packaging tools like .deb, .rpm, etc., which do not
> > generally take kindly to updating such things. For better or worse, the
> > filesystem *is* our "central database" these days.
>
> I don't think that's a
On Tue, 3 Aug 2010 22:25:01 +1000
Nick Coghlan wrote:
> On Tue, Aug 3, 2010 at 1:40 PM, Eli Bendersky wrote:
> > The first print out correctly specifies the line "def foo" is in. However,
> > the second one points to the line with "@dummydecorator" instead of "def
> > bar". [Python 2.6]
> >
> > T
> There is a tension between the two approaches: either you want
> "auto-discovery", or you want a system with explicit registration and
> only the registered plugins would be visible to the system.
I think both are necessary. A discovery API should be available, but the
library or application sh
Apparently you are not the only one experiencing it.
On #python-dev we get such notifications:
alanwilter roundup * #9485/signal.signal/signal.alarm not
working as expected: [new] I have this example code to illustrate a
problem I am ...
alanwilter roundup * #9486/signal.signal/signal.alarm not
Le mardi 03 août 2010 à 11:05 -0400, Raghuram Devarakonda a écrit :
> On Tue, Aug 3, 2010 at 10:14 AM, Guido van Rossum wrote:
>
> > What are the use cases for co_firstlineno? Even if it is for
> > displaying the source code, I can find virtue for both sides of this
> > argument.
>
> nose uses c
Hello,
While Lib/_threading_local.py is meant as a fallback Python
implementation of thread-local objects, it looks like it will never be
invoked in practice. The reason is that the thread-local code in
Modules/_threadmodule.c in unconditionally compiled. Furthermore,
_threading_local.py imports
On Tue, 03 Aug 2010 21:08:31 -0400
Steve Holden wrote:
> It's a little disappointing to discover that despite the relatively
> large number of developers who have received MSDN licenses from
> Microsoft, none if us have the time to make sure that the buildbots are
> green for the 2.6.6 release.
I
Le mercredi 04 août 2010 à 21:43 +1000, Richard Jones a écrit :
> On Wed, Aug 4, 2010 at 8:48 PM, Paul Moore wrote:
> > On 3 August 2010 20:30, Barry Warsaw wrote:
> >> Brian is looking at Windows now (the buildbots are
> >> a sad and sorry story).
> >
> > There seems to be something distinctly w
On Wed, 4 Aug 2010 15:39:16 +0200
Łukasz Langa wrote:
> 1. The patch makes KeyError behave analogically to IOError so that the first
> arg is now a message and the second is the actual key.
>
> >>> raise KeyError("Key not found", "a Scotsman on a horse")
> Traceback (most recent call last):
> ..
Le mercredi 04 août 2010 à 16:28 +0100, Paul Moore a écrit :
> On 4 August 2010 13:05, Antoine Pitrou wrote:
>
> >> I'm also quite confused by the test_smtpd failures that pop up on some
> >> of the test runs that I've had absolutely no luck reproducing
On Wed, 04 Aug 2010 16:45:37 -
exar...@twistedmatrix.com wrote:
>
> I don't think it's that hard to take a look at the end of the day (or
> before starting anything else the next morning). All it really takes is
> a choice on the part of each developer to care whether or not their
> change
On Wed, 04 Aug 2010 13:56:27 -0400
Steve Holden wrote:
>
> This whole discussion seems to make it clear that the release manager
> procedures are still ill-defined in certain areas. Otherwise a release
> manager could proceed by reading a web page an even, heaven help us,
> following specific lin
On Wed, 04 Aug 2010 23:53:22 +0200
Georg Brandl wrote:
> >
> > The hard part is to know *when* to look. As you might have noticed, the
> > Python test suite does not run in ten seconds, especially on some of the
> > buildbots -- it can take 1-2 there to complete.
>
> That should be "1-2 hours",
On Thu, 5 Aug 2010 07:57:07 +1000
Nick Coghlan wrote:
>
> +1 on what Fred said (i.e. post-moratorium, add a keyword-only "key"
> argument to KeyError, set "e.key" only if that argument is supplied,
> update the standard library to supply it and use a default message of
> "'Key not found: %r' % ke
Hello,
In issue #5319, the poster complains that redirecting stdout to a
misbehaving (pseudo-)file such as /dev/full should produce a non-zero
error code when the IO error happens at shutdown (when calling flush()
on stdout).
Is it a reasonable expectation? What would you think of making the
cha
On Mon, 9 Aug 2010 01:24:50 +0200 (CEST)
antoine.pitrou wrote:
> Author: antoine.pitrou
> Date: Mon Aug 9 01:24:50 2010
> New Revision: 83869
>
> Log:
> Issue #8524: Add a forget() method to socket objects, so as to put the
> socket into the closed state without closing the underlying file
> de
On Sun, 08 Aug 2010 18:49:50 -0400
Terry Reedy wrote:
>
> In the above example, I could say that Python did what it promised to do
> -- print something to the stdout stream, and that failure on flushing
> was outside its purview.
>
> I could also say that if one wants the flush to be considere
On Mon, 9 Aug 2010 22:16:24 +1000
Nick Coghlan wrote:
> On Mon, Aug 9, 2010 at 8:47 PM, antoine.pitrou
> wrote:
> > Author: antoine.pitrou
> > Date: Mon Aug 9 12:47:46 2010
> > New Revision: 83885
> >
> > Log:
> > Revert r83877 in order to fix compilation
>
> Is this still a problem even after
On Mon, 9 Aug 2010 22:34:18 +1000
Nick Coghlan wrote:
> On Mon, Aug 9, 2010 at 10:25 PM, Senthil Kumaran wrote:
> > Do you know what needs to done for making Modules/Setup to reflect
> > the changes in Modules/Setup.dist in the buildbots?
> > On local checkouts, the compilation goes fine.
>
> Th
On Sun, 08 Aug 2010 19:53:38 -0400
Eric Smith wrote:
> On 8/8/10 7:48 PM, Antoine Pitrou wrote:
> > On Mon, 9 Aug 2010 01:24:50 +0200 (CEST)
> > antoine.pitrou wrote:
> >> Author: antoine.pitrou
> >> Date: Mon Aug 9 01:24:50 2010
> >> New Revision: 83
On Wed, 11 Aug 2010 12:30:40 +1000
Nick Coghlan wrote:
>
> The second (#9396) came up in the context of the new cache decorators
> added to functools, and allowing applications to choose their own
> caching strategies. I suggested exposing the original (uncached)
> function, and Raymond suggested
On Tue, 10 Aug 2010 15:25:52 -0400
Terry Reedy wrote:
>
> Everyone working on the English-based Python distribution knows the
> order of the 26 English letters.
How does that solve anything?
I just had to decide whether “Jason V. Miller” had to come before or
after “Jay T. Miller” ('Jason' < '
Hello,
I would like to see “unit test needed” removed from the workflow menu in
the bug tracker. The reason is that we don't do test-driven development
(or, at least, most of us don't) and this stage entry is therefore
useless and confusing. Saying to someone that an unit test is needed
happens d
On Thu, 12 Aug 2010 11:02:29 -0400
Alexander Belopolsky wrote:
>
> I remember there was an idea somewhere to replace "patch" tag with a
> check-list with boxes for code, tests, and docs. I think that would
> be better than "unit test needed" stage.
To me the simpler the better. If there's a pat
On Thu, 12 Aug 2010 18:14:44 -0400
Glyph Lefkowitz wrote:
>
> On Aug 12, 2010, at 6:30 AM, Tim Golden wrote:
>
> > I don't care how many stats we're doing
>
> You might not, but I certainly do. And I can guarantee you that the
> authors of command-line tools that have to start up in under ten
On Fri, 13 Aug 2010 11:57:57 -0400
Barry Warsaw wrote:
> On Aug 12, 2010, at 09:10 AM, Fred Drake wrote:
>
> >Perhaps user configuration belongs in ~/.local/, or ~/.local/python/
> >(with attendant Windows & Mac OS noises); I don't really care where it
> >lands, because right now we just have a
On Tue, 17 Aug 2010 09:22:15 +
Kristján Valur Jónsson wrote:
> Hello there.
> I'd like to draw your attention to two feature requests / patches that I've
> subbmitted:
> http://bugs.python.org/issue9609
> http://bugs.python.org/issue9622
>
> These patches are the result of work that we have
Ok, I've looked at the patch and it's actually stackless-agnostic.
Regards
Antoine.
On Tue, 17 Aug 2010 12:31:30 +0200
Antoine Pitrou wrote:
> On Tue, 17 Aug 2010 09:22:15 +
> Kristján Valur Jónsson wrote:
> > Hello there.
> > I'd like to draw your
On Thu, 19 Aug 2010 17:28:19 +0200
Georg Brandl wrote:
> Am 19.08.2010 15:32, schrieb Nick Coghlan:
> > On Thu, Aug 19, 2010 at 9:55 PM, Éric Araujo wrote:
> >> Thanks for the replies.
> >>
> >> The dev FAQ is clear about regular use, it tells about the
> >> svnmerge-commit-message too, and peopl
On Thu, 19 Aug 2010 19:10:19 +0200 (CEST)
victor.stinner wrote:
> Author: victor.stinner
> Date: Thu Aug 19 19:10:18 2010
> New Revision: 84204
>
> Log:
> Fix os.get_exec_path() (code and tests) for python -bb
>
> Catch BytesWarning exceptions.
You should not catch warnings, but silence them us
On Sat, 21 Aug 2010 04:54:44 +0200 (CEST)
benjamin.peterson wrote:
> Log:
> alias macintosh to mac_roman #843590
>
[...]
>
> # mac_roman codec
> +'macintosh' : 'macintosh',
> 'macroman' : 'mac_roman',
I'm not sure what is achieved by aliasing 'macintosh' to its
On Thu, 26 Aug 2010 23:07:13 +0200 (CEST)
brett.cannon wrote:
> Author: brett.cannon
> Date: Thu Aug 26 23:07:13 2010
> New Revision: 84329
>
> Log:
> OSError is the exception raised when one tries to create a directory that
> already exists, not IOError.
It's probably simpler to catch all of th
On Sun, 29 Aug 2010 09:20:56 +1000
Nick Coghlan wrote:
>
> Four options come to mind:
>
> - just leave it out of the limited API, extensions can do their own
> thing to print objects
> - leave PyObject_Print out of the limited API, but create a
> PyObject_PrintEx that takes a Python IO stream vi
On Sun, 29 Aug 2010 18:41:45 +1000
Nick Coghlan wrote:
> On Sun, Aug 29, 2010 at 6:24 PM, Antoine Pitrou wrote:
> > On Sun, 29 Aug 2010 09:20:56 +1000
> > Nick Coghlan wrote:
> >>
> >> Four options come to mind:
> >>
> >> - just leave it
On Sun, 29 Aug 2010 22:16:57 +1000
Nick Coghlan wrote:
>
> However, since even platforms other than Windows aren't immune to
> version upgrades of the standard C runtime, I'm still more comfortable
> with the idea that the strict ABI should refuse to pass FILE* pointers
> across extension module
On Sun, 29 Aug 2010 22:56:56 +0200 (CEST)
giampaolo.rodola wrote:
> +with self.assertRaises(IOError) as err:
> +ssl.wrap_socket(socket.socket(), certfile=WRONGCERT)
> +self.assertEqual(err.errno, errno.ENOENT)
The assertEqual will never get executed since the previ
On Mon, 30 Aug 2010 07:31:34 +1000
Nick Coghlan wrote:
> Since part of the point of
> PEP 384 is to support multiple versions of the C runtime in a single
> process, [...]
I think that's quite a maximalist goal. The point of PEP 384 should be
to define a standard API for Python, (hopefully) spann
Le lundi 30 août 2010 à 22:18 +1000, Nick Coghlan a écrit :
>
> FILE* is very different from the other things you mention. Function
> call conventions and binary representations are defined in the C
> standard. FILE*, on the other hand, is explicitly called out as an
> opaque reference completely
On Tue, 31 Aug 2010 11:12:17 +0900
David Cournapeau wrote:
>
> > Hmm... that last point is a bit of any issue actually, since it also
> > flows the other way (changes made via the locale module won't be
> > visible to any extension modules using a different C runtime). So I
> > suspect mixing C r
> > So it means that, for example, a FileIO object couldn't be shared
> > between runtimes either? How about a socket object?
> > Do you want to forbid FileIO and socket objects as part of the API?
>
> Python objects don't have this concern: all methods of FileIO are implemented
> in a single fil
On Wed, 01 Sep 2010 10:23:42 +1200
Greg Ewing wrote:
> Daniel Stutzbach wrote:
>
> > Likewise, a FILE * isn't safe to pass around, unless I can guarantee
> > that the application really is one big happy family compiled against the
> > same version of the C library.
>
> Given that, it seems to
Le mercredi 01 septembre 2010 à 22:43 +1000, Nick Coghlan a écrit :
> On Wed, Sep 1, 2010 at 8:42 AM, Antoine Pitrou wrote:
> > After all, we don't usually try to workaround platform-specific
> > bugs (not as a low level such as the C API level); at worse, we mention
> &
On Thu, 2 Sep 2010 07:04:31 +1000
Nick Coghlan wrote:
> On Wed, Sep 1, 2010 at 10:54 PM, Antoine Pitrou wrote:
> > Please consider this: even without relying on PEP 384, using FILE*
> > is /already/ dangerous; because you might compile an extension with a
> > different
Hello all,
In issue #5506, I originally proposed that io.BytesIO objects support
the buffer protocol, to make it possible to access the internal buffer
without intermediate copies.
Then it came to me then perhaps it would be too automatic. So I'm
currently floating between:
- add implicit buffer
On Fri, 03 Sep 2010 10:04:12 +0200
Stefan Behnel wrote:
> Antoine Pitrou, 02.09.2010 22:35:
> > In issue #5506, I originally proposed that io.BytesIO objects support
> > the buffer protocol, to make it possible to access the internal buffer
> > without intermediate copies.
&g
On Fri, 3 Sep 2010 12:00:51 +0200 (CEST)
raymond.hettinger wrote:
> rv = set_discard_entry(so, &an_entry);
> -if (rv == -1)
> + if (rv == -1) {
> +Py_DECREF(key);
> return NULL;
> +}
> if (rv ==
On Fri, 3 Sep 2010 20:44:01 +1000
Nick Coghlan wrote:
>
> It actually strikes me as a fairly bad thing, so I think you're right
> to distrust it. Better to follow the precedent set with getvalue() and
> require an explicit call to getbuffer(). The fact there are two
> options (immutable copy via
On Fri, 3 Sep 2010 21:16:13 +1000
Nick Coghlan wrote:
> On Fri, Sep 3, 2010 at 8:56 PM, Antoine Pitrou wrote:
> > On Fri, 3 Sep 2010 20:44:01 +1000 Nick Coghlan wrote:
> > That's an interesting idea. I was planning to return a memoryview
> > object (in order to hide th
On Fri, 3 Sep 2010 09:32:22 -0700
Guido van Rossum wrote:
> >> > It could not be resized, but it could be modified (same as what happens
> >> > with bytearrays today). Actually, the buffer itself would be writable,
> >> > and allow modifying the BytesIO contents.
> >>
> >> You may need to be caref
On Sat, 04 Sep 2010 11:42:08 +0200
Éric Araujo wrote:
> > What about adding an intermediate namespace called "cache", so that the new
> > operations are available like this:
> >
> > print get_phone_number.cache.hits
> > get_phone_number.cache.clear()
> >
> > ?
> >
> > It's just a lit
On Sat, 04 Sep 2010 15:13:55 +0200
"Martin v. Löwis" wrote:
> > Please consider this: even without relying on PEP 384, using FILE*
> > is /already/ dangerous; because you might compile an extension with a
> > different compiler version than Python was compiled with.
>
> It's only dangerous *if*
On Sat, 4 Sep 2010 09:21:25 -0500
Daniel Stutzbach wrote:
>
> I have been using a similar LRU cache class to store items retrieved from a
> database. In my case, a decorator-paradigm wouldn't work well because I
> only want to cache a few of the columns from a much larger query, plus there
> are
On Sun, 5 Sep 2010 02:27:25 +0200 (CEST)
raymond.hettinger wrote:
> +
> +The common directory is "pyshared" and the file names are made distinct by
> +identifying the Python implementation (such as CPython, PyPy, Jython, etc.),
> the
> +major and minor version numbers, and optional build flags (
Hello Martin,
On Sat, 28 Aug 2010 12:04:10 +0200
"Martin v. Löwis" wrote:
> I have now started an initial patch for PEP 384, in the pep-0384 branch.
[...]
On http://bugs.python.org/issue9778 you elaborated on what the PEP would
entail in its current state:
“No, vice versa. The PEP promises tha
Hello,
What is needed in order to have write (i.e. push) access to the
hg.python.org repositories?
What are the URLs (for example for the "benchmarks" repository)?
Regards
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python
On Tue, 07 Sep 2010 10:11:41 +0200
Georg Brandl wrote:
> Am 07.09.2010 09:21, schrieb Dirkjan Ochtman:
> > On Tue, Sep 7, 2010 at 01:04, Antoine Pitrou wrote:
> >> What is needed in order to have write (i.e. push) access to the
> >> hg.python.org repositories?
> >
On Tue, 7 Sep 2010 23:01:17 +1000
Nick Coghlan wrote:
> > + # After the buffer gets released, we can resize the BytesIO again
> > + del buf
> > + support.gc_collect()
> > + memio.truncate()
>
> I've raised an RFE (http://bugs.python.org/issue9789) to point out
> that t
On Tue, 7 Sep 2010 02:38:15 +0200 (CEST)
raymond.hettinger wrote:
> Author: raymond.hettinger
> Date: Tue Sep 7 02:38:15 2010
> New Revision: 84574
>
> Log:
> Document which part of the random module module are guaranteed.
test_random fails here:
==
On Tue, 7 Sep 2010 06:44:52 +0200 (CEST)
raymond.hettinger wrote:
> Author: raymond.hettinger
> Date: Tue Sep 7 06:44:52 2010
> New Revision: 84576
>
> Log:
> Issues #7889, #9025 and #9379: Improvements to the random module.
This broke test_generators here:
[1/1] test_generators
Hello,
> My name is Prashant Kumar and I wish to contribute to the Python development
> process by helping convert certain existing python
> over to python3k.
>
> Is there anyway I could obtain a list of libraries which need to be ported
> over to python3k, sorted by importance(by importance i m
On Tue, 7 Sep 2010 10:29:48 +0200
Dirkjan Ochtman wrote:
> > and your URI is
> >
> > ssh://h...@hg.python.org/repos/benchmarks
> >
> > (That may change depending on the final setup, of course.)
>
> Yes, I think I'd prefer to just get rid of the /repos/ for the URLs
> (which makes http and ssh mor
On Tue, 7 Sep 2010 20:12:26 +0530
Prashant Kumar wrote:
> >
> > Right, and there are other standard library modules (cgi, ftplib, nntplib,
> > etc) that either need fixing or auditing as to how they handle bytes /
> > strings.
> >
>
> Sure I will look into this. Could you please point me towards
On Sun, 12 Sep 2010 06:12:42 +0200 (CEST)
raymond.hettinger wrote:
>
> -# Each link is stored as a list of length three: [PREV, NEXT, KEY].
> +# The back links are weakref proxies (to prevent circular references).
Are you sure this prevents anything? Since your list is circular,
forward
On Sun, 12 Sep 2010 19:38:33 +0200
"Martin v. Löwis" wrote:
> > On http://bugs.python.org/issue9778 you elaborated on what the PEP would
> > entail in its current state:
> >
> > “No, vice versa. The PEP promises that the ABI won't change until
> > Python 4. For any change that might break the ABI
On Mon, 13 Sep 2010 16:18:44 +0200 (CEST)
barry.warsaw wrote:
>
> -For an arbitrary package `foo`, you would see these files when the
> +For an arbitrary package `foo`, you might see these files when the
> distribution package was installed::
>
> -/usr/share/pyshared/foo.cpython-32m.so
>
On Mon, 13 Sep 2010 10:55:16 -0400
Barry Warsaw wrote:
> On Sep 13, 2010, at 04:36 PM, Antoine Pitrou wrote:
>
> >On Mon, 13 Sep 2010 16:18:44 +0200 (CEST)
> >barry.warsaw wrote:
> >>
> >> -For an arbitrary package `foo`, you would see these files when the
> >I meant how these decisions are implemented. Is there a configure
> >switch (there doesn't seem to be)? Does it require patching Python?
>
> Ah, no. Standard configure switches are used. Debian (inherited by Ubuntu)
> has a post-installation script for Python packages which create the .py
>
Hello,
Like the email package, nntplib in py3k is broken (because of
various bytes/str mismatches; I suppose the lack of a test suite didn't
help when porting).
I would like to take the opportunity to improve the API a bit; no heavy
re-architecting, but simply a bunch of changes to make it highe
On Tue, 14 Sep 2010 20:30:14 +1000
Nick Coghlan wrote:
> On Tue, Sep 14, 2010 at 8:17 PM, Antoine Pitrou wrote:
> >
> > Hello,
> >
> > Like the email package, nntplib in py3k is broken (because of
> > various bytes/str mismatches; I suppose the lack of a test s
On Tue, 14 Sep 2010 05:31:16 -0500
s...@pobox.com wrote:
>
> Antoine> Like the email package, nntplib in py3k is broken (because of
> Antoine> various bytes/str mismatches; I suppose the lack of a test
> Antoine> suite didn't help when porting).
>
> How heavily used is nntp these days
On Mon, 13 Sep 2010 18:58:31 -0400
Barry Warsaw wrote:
> On Sep 14, 2010, at 11:28 AM, Michael Foord wrote:
>
> > On 14/09/2010 11:17, Antoine Pitrou wrote:
> >> Hello,
> >>
> >> Like the email package, nntplib in py3k is broken (because of
> >>
On Wed, 15 Sep 2010 10:21:11 -0400
Steve Holden wrote:
>
> The question of when to declare 3.x the "official" release is
> interesting. I am inclined to say "when there's at least one other
> implementation at 3.2" - even if CPython is then at 3.3 or 3.4.
I don't think that's a good criterion. 95
On Wed, 15 Sep 2010 11:11:14 -0700
Guido van Rossum wrote:
> Given that wsgiref is in the stdlib, I think we should hold up the 3.2
> release (and even the first beta) until this is resolved, unless we
> can convince ourselves that it's okay to delete wsgiref from the
> stdlib (which sounds unlike
On Wed, 15 Sep 2010 19:55:16 -0500
Jacob Kaplan-Moss wrote:
> On Wed, Sep 15, 2010 at 6:31 PM, Jesse Noller wrote:
> > My goal (personally) is to make sure python 3.2 is perfectly good for use
> > in web applications, and is therefore a much more interesting porting
> > target for web projects/
On Thu, 16 Sep 2010 17:27:50 +0200
Georg Brandl wrote:
> Maybe you want to mention *who* warns?
I suppose it's the -3 flag:
$ ~/cpython/27/python -3 -c "1/0"
-c:1: DeprecationWarning: classic int division
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: integer divisi
On Thu, 16 Sep 2010 11:30:12 -0400
"R. David Murray" wrote:
>
> And then BaseHeader uses self.lit.colon, etc, when manipulating strings.
> It also has to use slice notation rather than indexing when looking at
> individual characters, which is a PITA but not terrible.
>
> I'm not saying this is
On Thu, 16 Sep 2010 16:51:58 -0400
"R. David Murray" wrote:
>
> What do we store in the model? We could say that the model is always
> text. But then we lose information about the original bytes message,
> and we can't reproduce it. For various reasons (mailman being a big one),
> this is not a
Le jeudi 16 septembre 2010 à 22:51 -0400, R. David Murray a écrit :
> > > On disk, using utf-8,
> > > one might store the text representation of the message, rather than
> > > the wire-format (ASCII encoded) version. We might want to write such
> > > messages from scratch.
> >
> > But then the us
On Fri, 17 Sep 2010 11:40:12 +0200
Sébastien Sablé wrote:
> Hi Martin,
>
> I have started to correct quite a lot of issues I have with Python on
> AIX, and since I had to test quite a lot of patchs, I though it would be
> more convenient to setup a buildbot for that platform.
>
> So I now have
On Sun, 19 Sep 2010 12:19:44 +0200
Victor Stinner wrote:
> Le dimanche 19 septembre 2010 01:05:45, Greg Ewing a écrit :
> > I don't follow. Trusted functions such as proxy() shouldn't
> > be sharing a __builtins__ dict with sandboxed code.
> > (...)
> > So give each program its own copy of __built
For the record, the code is pretty much done now:
http://bugs.python.org/issue9360
Regards
Antoine.
On Tue, 14 Sep 2010 12:17:44 +0200
Antoine Pitrou wrote:
>
> Hello,
>
> Like the email package, nntplib in py3k is broken (because of
> various bytes/str mismatches; I suppos
On Mon, 20 Sep 2010 09:31:45 -0500
Tom Browder wrote:
>
> Can anyone explain the two different "default" installations I got?
>
> It seems to me I should force the Ubuntu-style installation by the
> "--with-universal-archs=64-bit" configure option, and I will try that
> on Debian while I await
Hello David,
On Mon, 20 Sep 2010 16:42:10 -0400
David Bolen wrote:
> Hirokazu Yamamoto writes:
>
> > Hello. I've sent following mail to buildbot manager,
> > but I found that buildbot page saids the problem of unsable
> > bot should be sent to python-...@python.org. So I'll do it.
>
> (I'm fi
On Mon, 20 Sep 2010 19:02:33 -0400
David Bolen wrote:
>
> Looks like some issue with using bytes for os.path.exists - I
> "borrowed" a Python 3.x build currently in the tree as part of build
> 1611 and tried:
>
> d...@buildbot-win7 ~
> $ buildarea/3.x.bolen-windows7/build/pcbuild/python_d
> Pyth
On Mon, 20 Sep 2010 19:02:33 -0400
David Bolen wrote:
>
> d...@buildbot-win7 ~
> $ buildarea/3.x.bolen-windows7/build/pcbuild/python_d
> Python 3.2a2+ (py3k, Sep 20 2010, 18:49:03) [MSC v.1500 32 bit (Intel)] on
> win32
>
> Type "help", "copyright", "credits" or "license" for more information.
On Tue, 21 Sep 2010 02:34:46 +0200
Éric Araujo wrote:
> > Log:
> > Remove references to read() and write() methods, which are useless
> > synonyms of recv() and send()
>
> Unless I’m mistaken, ssl.SSLSocket.write is still useful for use with
> print, pprint and maybe other functions,
Hmm, sorry?
On Wed, 22 Sep 2010 00:10:01 +0900
"Stephen J. Turnbull" wrote:
>
> But I don't know whether the web apps programmers will be satisfied
> with such a minimal API.
Web app programmers will generally go through a framework, which
handles encoding/decoding for them (already so in 2.x).
> And there
On Tue, 21 Sep 2010 12:09:44 -0400
"P.J. Eby" wrote:
> While the Web-SIG is trying to hash out PEP 444, I thought it would
> be a good idea to have a backup plan that would allow the Python 3
> stdlib to move forward, without needing a major new spec to settle
> out implementation questions.
I
On Tue, 21 Sep 2010 20:16:52 -0400
Jack Diederich wrote:
> On Tue, Sep 21, 2010 at 7:58 PM, Mark Lawrence
> wrote:
> > I'm rather sad to have been sacked, but such is life. I won't be doing any
> > more work on the bug tracker for obvious reasons, but hope that you who have
> > managed to keep
2901 - 3000 of 4909 matches
Mail list logo
