On Thu, 23 Sep 2010 00:29:23 +0900
"Stephen J. Turnbull" wrote:
> Guido van Rossum writes:
>
> > I would recommend that in the future more attention is paid to
> > "documenting" publicly that someone's being booted out was
> > inevitable, by an exchange of messages on python-dev (or
> > pytho
On Thu, 23 Sep 2010 13:32:07 +0900
"Stephen J. Turnbull" wrote:
>
> Triaging and closing bug reports are
> not the only functions of the tracker, and in fact they are subsidiary
> to actual bug-fixing work.
+1. What we really need is people analyzing issues, posting patches or
reviewing existing
On Wed, 22 Sep 2010 21:24:49 -0400
"R. David Murray" wrote:
>
> > deputed tracker authority/ies. Not everyone has the same idea about how
> > to handle the various fields and processes. Who decides in cases of
> > disagreement?
>
> We discussed this a while back and I don't think we really hav
On Thu, 23 Sep 2010 00:29:51 -0400
Fred Drake wrote:
> On Wed, Sep 22, 2010 at 10:38 PM, Brett Cannon wrote:
> > the first thing on the agenda is a complete rewrite of the developer
> > docs and moving them into the Doc/ directory
>
> I'd like to know why you think moving the developer docs int
On Thu, 23 Sep 2010 10:16:01 -0400
"R. David Murray" wrote:
> On Thu, 23 Sep 2010 23:35:02 +1000, Nick Coghlan wrote:
> > On Thu, Sep 23, 2010 at 8:11 PM, Antoine Pitrou wrote:
> > > The practicality argument of being able to edit those docs without
> > >
On Thu, 23 Sep 2010 10:53:55 -0400
Barry Warsaw wrote:
>
> Of course, if the consensus is that wikis are just a waste of time and do more
> harm than good, then we should shut ours down. (I don't agree it is though.)
I don't think they are a waste of time. However, as you and Dirkjan
pointed ou
On Thu, 23 Sep 2010 11:57:19 -0400
Barry Warsaw wrote:
> On Sep 23, 2010, at 05:32 PM, Antoine Pitrou wrote:
>
> >I don't think they are a waste of time. However, as you and Dirkjan
> >pointed out, a wiki needs some "gardening" to take care of its
> >stru
The getlogin test fails on many Unix buildbots, either with errno 2
(ENOENT) or 22 (EINVAL) or "OSError: unable to determine login name":
==
ERROR: test_getlogin (test.test_os.LoginTests)
-
On Fri, 24 Sep 2010 13:38:44 +0200
"Amaury Forgeot d'Arc" wrote:
> 2010/9/24 Antoine Pitrou :
> >
> > The getlogin test fails on many Unix buildbots, either with errno 2
> > (ENOENT) or 22 (EINVAL) or "OSError: unable to determine login name":
>
&
On Fri, 24 Sep 2010 11:07:59 +0200
Éric Araujo wrote:
> How about revamping the type/versions fields?
>
> Issue type
> () Feature request (blocked by moratorium: () yes () no)
> () Bug (found in: [] 2.7 [] 3.1 [] py3k)
> () Security bug (found in: [] 2.5 [] 2.6 [] 2.7 [] 3.1 [] py3k)
>
> I’m get
> > But we also have "performance", "crash", "resource usage"... Are we
> > suggesting we devise a separate list box for each of these issue types?
>
> I must admit, I've never actually found much use for those additional
> options. If I'm flagging a bug I'll nearly always mark it "behaviour",
>
On Fri, 24 Sep 2010 07:29:40 -0700
Guido van Rossum wrote:
> It will have to be a new API -- normcase() at
> least is *intended* to return a case-flattened name on OSes where
> case-preserving filesystems are the default, and changing it to look
> at the filesystem would break too much code. For a
Le samedi 25 septembre 2010 à 00:42 +1000, Nick Coghlan a écrit :
> >
> > I have often used searches on "performance" or "resource usage" to find
> > what was needing a review or a patch. I think it would be a mistake to
> > remove those two categories.
>
> That purpose would be served just as wel
> > But how should a performance improvement be filed? Bug? Feature request?
> > Or should "feature request" be renamed "improvement"?
>
> It's a feature request (since we won't backport it unless there is a
> genuine performance problem being addressed as a bug fix). Whether
> that warrants chan
On Fri, 24 Sep 2010 15:14:32 -0400
Tim Peters wrote:
> Looks like 2.7 changes introduced to exempt dicts and tuples from
> cyclic gc if they obviously can't be in cycles has some unintended
> consequences. Specifically, if an extension module calls
> PyObject_GC_UnTrack() on a dict it _does not w
On Sat, 25 Sep 2010 00:04:23 +0200 (CEST)
alexander.belopolsky wrote:
> Author: alexander.belopolsky
> Date: Sat Sep 25 00:04:22 2010
> New Revision: 85000
>
> Log:
> This should fix buildbot failure introduced by r84994
Can you also backport it to 2.7?
Thanks
Antoine.
__
On Sat, 25 Sep 2010 19:02:06 +0200
Georg Brandl wrote:
> Am 25.09.2010 18:53, schrieb Terry Reedy:
> > On 9/25/2010 7:11 AM, Georg Brandl wrote:
> >
> >> I'll bother Ezio when he's back. It just feels strange to me that the bit
> >> of statistic I feel is most interesting -- whether there are l
On Mon, 27 Sep 2010 12:25:17 -0400
Alexander Belopolsky wrote:
> On Mon, Sep 27, 2010 at 11:28 AM, Barry Warsaw wrote:
> ..
> > If so, then I say in hg, nuke the tags we don't care about and sanitize the
> > release tags to something that obvious and can't collide (e.g. r311 is 3.1.1
> > or 3.11
Hello,
While trying to solve #3873 (poor performance of pickle on file
objects, due to the overhead of calling read() with very small values),
it occurred to me that the prefetching facilities offered by
BufferedIOBase are not flexible and efficient enough.
Indeed, if you use seek() and read(),
On Mon, 27 Sep 2010 23:45:45 -0400
Steve Holden wrote:
> On 9/27/2010 11:27 PM, Benjamin Peterson wrote:
> > 2010/9/27 Meador Inge :
> >> which, as seen in the trace, is because the 'detect_encoding' function in
> >> 'Lib/tokenize.py' searches for 'BOM_UTF8' (a 'bytes' object) in the string
> >> t
On Tue, 28 Sep 2010 04:44:08 +0200
Jesus Cea wrote:
>
> But in python 2.7 release, CObject is marked as deprecated (arg!), so
> when executing python with -We (mark warnings as errors), bsddb fails.
By "fails" you mean "crashes the interpreter".
While the deprecation warning can be discussed, bs
On Wed, 29 Sep 2010 10:06:57 +0200
Hagen Fürstenau wrote:
> > Ow... I've always assumed that seek() is essentially free, because
> > that's how a typical OS kernel implements it. If seek() is bad on
> > GzipFile, how hard would it be to fix this?
>
> I'd imagine that there's no easy way to make a
On Wed, 29 Sep 2010 09:03:29 +0200
Dirkjan Ochtman wrote:
>
> Anyway, I don't think using Bitbucket buys us much. It could be nice
> to keep a mirror there for redundancy and because it might make
> contributing slightly easier for non-committers, but it won't allow
> doing all kinds of custom ho
Hello,
> I'd like to ask your opinion on this change; I think it should be reverted
> or at least made silent by default. Basically, it prints a warning like
>
> gc: 2 uncollectable objects at shutdown:
> Use gc.set_debug(gc.DEBUG_UNCOLLECTABLE) to list them.
>
> at interpreter
Le mercredi 29 septembre 2010 à 07:27 -0500, Benjamin Peterson a écrit :
> >
> > I would like to piggy-back on this discussion to suggest further
> > warnings (either by default, or switchable).
> >
> > One feature I've often considered would be to add a warning in FileIO
> > and socket dealloc if
On Wed, 29 Sep 2010 11:32:19 -0700
Guido van Rossum wrote:
> I would like to recommend that the Python core developers start using
> a code review tool such as Rietveld or Reviewboard. I don't really
> care which tool we use (I'm sure there are plenty of pros and cons to
> each) but I do think we
Guido, Brett,
On Wed, 29 Sep 2010 11:47:51 -0700
Brett Cannon wrote:
>
> The other option (as discussed on Buzz) is to add Rietveld's upload.py
> to Misc/ and tell people to use that to submit the patch.
It sounds like a good option (or, even better, a customized version as
suggested by Daniel
> > Well, I would assume people are working from a checkout. Patches from
> > an outdated checkout simply would fail and that's fine by me.
>
> Ok, but that's an extra barrier for contributions. Lots of people when
> asked for a patch just modify their distro in place and you can count
> yourself
Le mercredi 29 septembre 2010 à 13:35 -0700, Brett Cannon a écrit :
>
> Well, we can start with strongly worded suggestions that patches
> submitted using Rietveld will typically get priority over patches
> submitted just to the issue tracker and that this means doing it from
> a checkout.
But wi
On Wed, 29 Sep 2010 13:56:46 -0700
Brett Cannon wrote:
> On Wed, Sep 29, 2010 at 13:31, Alexander Belopolsky
> wrote:
> > On Wed, Sep 29, 2010 at 4:23 PM, Guido van Rossum wrote:
> > ..
> >> But maybe with Hg it's less of a burden to ask people to use a checkout.
> >>
> >
> > I thought with Hg i
On Wed, 29 Sep 2010 23:05:38 +0200
"M.-A. Lemburg" wrote:
>
> The codec is scheduled to be added back to Python3.
>
> However, it's main use is in working on whole chunks of
> data rather than the line-by-line approach you're after.
> This is provided by the codec's incremental encoder/decoders,
Le mercredi 29 septembre 2010 à 17:41 -0400, Chris Bergstresser a
écrit :
> On Wed, Sep 29, 2010 at 5:23 PM, Antoine Pitrou wrote:
> > Anyway, the obvious way to write line-by-line to a bz2 file is to use
> > the BZ2File class!
>
>The BZ2File class does not allow y
On Wed, 29 Sep 2010 17:30:10 -0400
Barry Warsaw wrote:
> One other thought: IME patches in general are suboptimal to branches, so I
> think we should be encouraging people to publish their branches publicly for
> review. A diff is a decent way to get feedback about code changes, but that's
> ofte
On Wed, 29 Sep 2010 23:58:05 +0200
"Martin v. Löwis" wrote:
> > That shouldn't be too hard. Someone just has to create an App Engine
> > project and handle the deployment. I guess the trickiest part is
> > making sure enough people have admin access so multiple people can
> > update the website, e
On Thu, 30 Sep 2010 14:52:18 -
exar...@twistedmatrix.com wrote:
> >
> >Regardless of the tool(s) used, code reviews are a fantastic
> >equalizer. If you have long time, experienced developers "submitting"
> >to the same rules that newer contributors have to follow then it helps
> >remove the id
Hello,
It seems the py3k docs (both dev and 3.1) haven't been rebuilt for a few
days. Is there anything that needs to be done to trigger rebuilding?
Thank you,
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
On Fri, 1 Oct 2010 20:06:57 -0400
Barry Warsaw wrote:
>
> With my branch, you'll end up with this in /tmp/python:
>
> bin/python3.2m - the normal build binary
> bin/python3.2dmu - the wide+pydebug build binary
> bin/python3.2m-config
> bin/python3.2dmu-config
Do users really w
On Sat, 02 Oct 2010 09:44:16 +0200
"Martin v. Löwis" wrote:
>
> I could accept that a suffix is parameter to configure (or some such),
> and then gets used throughout. By default, Python will not add a suffix.
> However, I still wonder why people couldn't just install Python in a
> different pref
On Sat, 02 Oct 2010 22:14:28 +0200
Jesus Cea wrote:
>
> My idea is to convert the CObject exception in bsddb to print a warning
> like "CObject creation failed. The bsddb.cAPI will be not available.
> Reason is: ".
>
> Is there a "canonical way" of doing this?. Sorry if the answer is trivial
Hello,
On Sat, 02 Oct 2010 22:03:57 +0200
"Martin v. Löwis" wrote:
> Following up to the recent thread, I have now integrated Rietveld
> into Roundup. This is a rough draft still, and highly experimental.
> Please try it out, but expect that it may be necessary to discard
> all data (including c
Le samedi 02 octobre 2010 à 22:55 +0200, "Martin v. Löwis" a écrit :
>
> > 2) if I look at http://bugs.python.org/issue9962, only the second patch
> > of all three has been enabled for review. Yet they were all created
> > through "svn diff" against a recent py3k checkout.
>
> They had both the s
On Mon, 4 Oct 2010 14:41:11 -0400
Barry Warsaw wrote:
>
> For a distro, all those Python binaries have to go in /usr/bin. We already
> symlink /usr/bin/python to pythonX.Y so I don't see the harm in a few extra
> symlinks.
Why would a distro want to provide all combinations of Python builds?
O
On Mon, 4 Oct 2010 16:01:17 -0400
Barry Warsaw wrote:
> >
> >Why would a distro want to provide all combinations of Python builds?
>
> Maybe not all, but definitely several. At least a normal build and a debug
> build, but a wide unicode build possibly also.
What is the point of shipping a diff
On Tue, 05 Oct 2010 12:39:00 +0100
Michael Foord wrote:
>
> 1. rename the old file 'python-wing3.wpr' and rename 'python-wing4.wpr'
> to 'python-wing.wpr'
> 2. delete the wing 3 project file altogether and rename
> 'python-wing4.wpr' to 'python-wing.wpr'
> 3. stay with versioned project file na
On Tue, 05 Oct 2010 17:18:18 +0100
Michael Foord wrote:
> >
> > Generally I'm +0 on relative imports as a whole.
>
> As the OP pointed out, for code that may be *included* in other projects
> there is no other choice. This is often useful for packages shared
> between one or two projects that n
On Tue, 05 Oct 2010 17:06:40 +0200
"Martin v. Löwis" wrote:
> > I can probably run a build slave on one of my boxes (Gentoo, Athlon 64
> > x2). Where are the setup docs?
>
> http://wiki.python.org/moin/BuildBot
By the way, is the distinction between "stable" and "unstable" builders
still relevan
Le mardi 05 octobre 2010 à 13:28 -0400, Darren Dale a écrit :
> >>
> >> As the OP pointed out, for code that may be *included* in other projects
> >> there is no other choice. This is often useful for packages shared
> >> between one or two projects that nonetheless don't warrant separate
> >> dist
On Tue, 5 Oct 2010 14:17:47 -0400
Darren Dale wrote:
> >> Thats not the point though. Due to compatibility issues, maybe I don't
> >> want to expose the code at the top level. Maybe the foo package is
> >> distributed elsewhere as a top-level package, but I need to use an
> >> older version due to
On Tue, 05 Oct 2010 22:55:41 +0200
"Martin v. Löwis" wrote:
>
> I guess somebody would need to do monitoring on them, and ping operators
> if the buildbot is down for an extended period of time. Feel free to
> ping any operator whenever you notice that a slave is down (they do get
> an automated
On Thu, 07 Oct 2010 23:04:54 +0200
"Martin v. Löwis" wrote:
>
> However, if I get something like
>
> diff -r e981b6cc56b0 Include/longintrepr.h
> --- a/Include/longintrepr.h Thu Oct 07 03:12:19 2010 +0200
> +++ b/Include/longintrepr.h Thu Oct 07 13:53:41 2010 +0200
>
> I have no clue where
Le jeudi 07 octobre 2010 à 23:17 +0200, "Martin v. Löwis" a écrit :
> > As I said, most patches are supposed to be produced against py3k HEAD,
> > so you could try just that as the primary heuristic.
>
> I think this is impractical. There are tons of patches (the majority)
> which are in the track
On Tue, 5 Oct 2010 10:08:59 -0700
Stephen Hansen wrote:
> On Sat, Oct 2, 2010 at 1:37 PM, "Martin v. Löwis" wrote:
>
> > > I'm already running a Jython buildslave on an Intel Mac Pro which is
> > > pretty underused - I'd be happy to run a CPython one there too, if
> > > it'd be worthwhile.
> >
>
Hi,
> The failure is happening just because it can't possibly succeed, I set
> up the account for the buildbot in such a way that it has no access to
> a GUI context. I'm going to rectify that today so I can properly test
> TK.
Well, a nice thing would be for tests to be properly skipped in this
On Fri, 8 Oct 2010 10:26:36 -0400
Barry Warsaw wrote:
> >- query pypi
> >- browse what's installed
> >- install/remove projects
> >- create releases and upload them
> >
> >pkg_manager ?
>
> No underscores, please. :)
>
> Actually, a decent wrapper script could just be called 'setup'. My
> comma
On Fri, 8 Oct 2010 11:04:35 -0400
Toshio Kuratomi wrote:
>
> In the larger universe of programs, it might make for more intuitive
> remembering of the command to use a prefix (either py or python) though.
>
> python-setup is a lot like python setup.py
> pysetup is shorter
> pyegg is even shorte
On Fri, 8 Oct 2010 10:02:59 -0700
Stephen Hansen wrote:
>
> And long story short, it gets to 201 and runs test_cmd_line in the same
> order as the buildbot did, and it succeeds too, and I curse the gods of the
> netherworld, and am stumped with how to proceed. Two separate buildbot runs
> and thi
Congratulations Stephen, you are now the owner of our first green OS X
buildbot!
cheers
Antoine.
On Fri, 8 Oct 2010 08:11:13 -0700
Stephen Hansen wrote:
[snip]
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinf
> If someone wants to throw an issue my way, I can take a look at
> dumping stdout/stderr from the various test_cmd_line tests (I may not
> get to it until post-beta1 though).
It's done in r85324.
Regards
Antoine.
___
Python-Dev mailing list
Python-
On Sun, 10 Oct 2010 13:57:21 -0500
"Paul McGuire" wrote:
>
> Any comments? Interest? Should I write up a PEP? Go back to my pyparsing
> hole?
Generally, these things are discussed on python-ideas first. I don't
think a PEP required for a single function, but you'll have to convince
people that
On Tue, 12 Oct 2010 01:11:24 +0200
Giampaolo Rodolà wrote:
> Wouldn't be kinda weird that one can open the command prompt and run
> "pysetup" but not "python" on Windows?
If you add C:\PythonXY to your path, you can run "python".
Regards
Antoine.
__
On Wed, 13 Oct 2010 16:55:03 +0300
anatoly techtonik wrote:
>
> Is there a public list of annoyances for Python 3 that I can check to
> see if my change is already scheduled for Python 4 and vote for it?
No, there isn't. If you want to know what Python 3 is about, you can :
- read the docs
- rea
On Wed, 13 Oct 2010 22:55:21 +0200
"Martin v. Löwis" wrote:
> I have appointed Antoine Pitrou as the authority/manager
> for which build slave are considered stable. If you want
> to get a certain slave elevated or demoted, you have to
> convince him.
Thank you Martin!
On Wed, 13 Oct 2010 15:08:24 -0700
Stephen Hansen wrote:
> On 10/13/10 2:47 PM, Antoine Pitrou wrote:
> > (you'll notice that we have currently no 64-bit Windows machine although
> > 64-bit support under Windows has specific issues)
>
> Provided its not a problem that i
Hello,
In the http://bugs.python.org/issue10093 discussion, I proposed to add a
specific warning category for unclosed files. The rationale is that
these warnings will happen in destructors and therefore filtering by
line number and filename doesn't make sense. So a new category would be
useful i
On Thu, 14 Oct 2010 11:25:39 +0200
Antoine Pitrou wrote:
>
> Hello,
>
> In the http://bugs.python.org/issue10093 discussion, I proposed to add a
> specific warning category for unclosed files. The rationale is that
> these warnings will happen in destructors and therefore f
On Thu, 14 Oct 2010 08:07:46 +0200
Georg Brandl wrote:
>
> Very nice. http://www.python.org/dev/buildbot/stable/ is completely
> green at the moment -- which means that I can now indeed take failures
> seriously in the future. Previously, two of four "stables" for py3k
> were not even connected
On Thu, 14 Oct 2010 13:04:01 -0400
Barry Warsaw wrote:
> Posting this here first, though it's looking less like a Python bug and more
> like an environment problem, or issue with something in Ubuntu.
>
> I'm running the regular test suite for the py3k branch and seeing this failure
> on Ubuntu 10
On Sat, 16 Oct 2010 15:14:10 +0200 (CEST)
victor.stinner wrote:
> Author: victor.stinner
> Date: Sat Oct 16 15:14:10 2010
> New Revision: 85569
>
> Log:
> Issue #9713, #10114: Parser functions (eg. PyParser_ASTFromFile) expects
> filenames encoded to the filesystem encoding with surrogateescape e
On Mon, 18 Oct 2010 21:31:24 +0200
Georg Brandl wrote:
>
> This is probably sophistry, but if an issue is invalid, it doesn't need
> a patch :)
Not only, but it generally gets closed too.
> The first stage seems to be "unit test needed" anyway, which
> sounds to me a bit like "needs to be check
On Mon, 18 Oct 2010 22:27:06 -0500
Ron Adam wrote:
>
> Could something like (or parts of) the following work? It would have
> assignment and module keywords items as well.
Well, this is very nice, except that the more complicated the form is,
the less likely people are to fill it (and even les
Hello Jesus,
> Current Python lacks support for "aio_*" syscalls to do async IO. I
> think this could be a nice addition for python 3.3.
>
> If you agree, I will create an issue in the tracker. If you think the
> idea is of no value, please say so for me to move on. Maybe an 3th party
> module,
Le mercredi 20 octobre 2010 à 00:48 +0200, "Martin v. Löwis" a écrit :
> > Also, the canonical way to do file I/O in Python 3 is the `io` lib,
> > therefore it would be a bit of a shame to have separate, non-integrated
> > `aio_*` functions.
>
> I disagree. We also have posix.open, posix.dup, etc.
On Wed, 20 Oct 2010 20:01:56 -0500
Ron Adam wrote:
>
> On Ubuntu, I use python, python2.7, python3.1, python3.2 and that is what I
> type to use that particular version. The -m option seems to me to be the
> easiest to do and works with all of these.
>
> python2.7 -m setup
> python3
On Fri, 22 Oct 2010 09:41:09 -0500
Benjamin Peterson wrote:
> 2010/10/22 :
> > Instances of classes don't refer to the module their class is defined in.
> > It seems more likely that the reason the module is garbage collected is
> > that there really is nothing which refers to it anymore.
>
> I
On Fri, 22 Oct 2010 17:37:53 +0200
Stefan Behnel wrote:
>
> I think the general problem is that "the module" can be a pretty broad
> thing, potentially referring to all sorts of stuff such as (usually)
> several other modules.
I wouldn't think of unloading modules as a general problem. We shou
On Fri, 22 Oct 2010 18:08:20 +0200 (CEST)
Python tracker wrote:
>
> ACTIVITY SUMMARY (2010-10-15 - 2010-10-22)
> Python tracker at http://bugs.python.org/
>
> To view or respond to any of the issues listed below, click on the issue.
> Do NOT respond to this message.
>
> Issues stats:
> open
Hello everybody,
Who is doing multiprocessing maintenance these days? I thought Ask
Solem had been given commit privs for that, but I haven't seen any
activity from him; and Jesse is, mostly, absent. Is anyone working on
the multiprocessing issues?
(no, I'm not planning to address them :-))
che
On Wed, 13 Oct 2010 17:50:49 -0500
Brian Curtin wrote:
[...]
>
> I have a Server 2008 R2 x64 box with the full Visual Studio that I could add
> to the buildbot fleet. It's a dual core with 4 GB of RAM, plenty of disk
> space, and it runs 24/7.
The adventures of http://bugs.python.org/issue9778 s
Hello,
The first 3.2 beta is scheduled by Georg for November 13th.
What would you think of scheduling a bug week-end one week later, that
is on November 20th and 21st? We would need enough core developers to
be available on #python-dev.
Regards
Antoine.
___
> You mean: actively feeling responsible for it? I guess nobody - as for
> many other modules in the standard library.
>
> Or do you mean: who is willing to work on it, in principle?
Both. Originally the module is/was meant to be officially maintained by
Jesse, as far as I understand. But bugs f
On Mon, 25 Oct 2010 19:37:23 +0200 (CEST)
victor.stinner wrote:
>
> -if (argc == 0)
> -return;
> argv0 = argv[0];
Well, are you sure argv[0] is valid when argc is 0?
Regards
Antoine.
___
Python-Dev mailing list
Python-Dev@python.o
On Mon, 25 Oct 2010 11:32:42 -0400
"R. David Murray" wrote:
> On Mon, 25 Oct 2010 12:22:24 -0200, Rodrigo Bernardo Pimentel
> wrote:
> >> Am 23.10.2010 19:08, schrieb Antoine Pitrou:
> >>> The first 3.2 beta is scheduled by Georg for November 13th.
> >
Hello,
The development team of the Python interpreter (a.k.a python-dev) is
organizing a bug week-end on Saturday 20th and Sunday 21st of November.
We would like to encourage anyone who feels interested in participating
to give it a try. Contributing to Python is much less intimidating than
it s
On Mon, 25 Oct 2010 10:01:43 -0400
Jesse Noller wrote:
> On Sat, Oct 23, 2010 at 2:10 PM, "Martin v. Löwis" wrote:
> >> Who is doing multiprocessing maintenance these days? I thought Ask
> >> Solem had been given commit privs for that, but I haven't seen any
> >> activity from him; and Jesse is,
On Tue, 26 Oct 2010 10:42:27 -0700
Ned Deily wrote:
> In article <20101026085124.4c684...@mission>,
> Barry Warsaw wrote:
> > On Oct 26, 2010, at 09:19 PM, Nick Coghlan wrote:
> > >On Tue, Oct 26, 2010 at 5:31 PM, Georg Brandl wrote:
> > >> This looks more like "Add gitignore". Do we really w
On Tue, 26 Oct 2010 12:34:30 -0700
Raymond Hettinger wrote:
>
> FWIW, it wasn't that big (approx 2500 lines).
> The argparse, difflib, doctest, pickletools, pydoc, tarfile modules
> are about the same size and the decimal module is even larger.
> Please don't split those.
I think it comes down
On Wed, 27 Oct 2010 10:13:12 +0800
Kristján Valur Jónsson wrote:
> Although 2.7 has the new buffer interface and memoryview
> objects, these are widely not accepted in the built in modules.
That's true, and slightly unfortunate. It could be a reason for
switching to 3.1/3.2 :-)
> IMHO this is un
On Tue, 26 Oct 2010 22:06:37 -0400
Alexander Belopolsky wrote:
>
> While I appreciate your and Michael's eloquence, I don't really see
> why five 400-line modules are necessarily easier to maintain than one
> 2000-line module. Splitting code into modules is certainly a good
> thing when the resu
> >Here are micro-benchmarks under 3.2:
>
> > $ ./python -m timeit -s "x = b'x'*1" "x[:100]"
> > 1000 loops, best of 3: 0.134 usec per loop
> > $ ./python -m timeit -s "x = memoryview(b'x'*1)" "x[:100]"
> > 1000 loops, best of 3: 0.151 usec per loop
>
> That's weird. The greedy
On Wed, 27 Oct 2010 20:00:10 +0800
Kristján Valur Jónsson wrote:
> Calling getbuffer on a bytearray or a bytes object should
> be really cheap, so I still don't accept this as a matter of fact
> situation.
It *is* cheap. It's just that copying a short slice is dirt cheap as
well.
Of course, it y
On Wed, 27 Oct 2010 23:05:37 -0500
Benjamin Peterson wrote:
> 2010/10/27 Kristján Valur Jónsson :
> > Firstly, the ease of integrating changes. It would be possible to port
> > those bugfixes that release-27 gets, and also backport selected things from
> > py3k using the tools already in place su
On Thu, 28 Oct 2010 15:54:50 +0200
Georg Brandl wrote:
> Am 28.10.2010 15:14, schrieb "Martin v. Löwis":
> >> Furthermore, our server is fairly complex: we're using quite some
> >> libraries to do different jobs, and one of the approaches (not the
> >> only one) that we're taking to deal with this
On Fri, 15 Oct 2010 17:38:47 +0200
Sébastien Sablé wrote:
>
> Could you please take a look at those modifications in master.cfg,
> provide me some password for the bot slaves and apply the corrections in
> those issues?
About the master.cfg modifications: there should be no need for
separate e
On Thu, 28 Oct 2010 10:25:28 -0700
Ian Bicking wrote:
>
> Thinking about language features and core type this seems reasonable, but
> with the standard library this seems less reasonable -- there's lots of
> conservative changes to the standard library which aren't bug fixes, and the
> more the s
On Fri, 29 Oct 2010 10:10:31 +0800
Kristján Valur Jónsson wrote:
>
> What finally drove me to write the original post, was that working with
> the new bytearray and memoryview object in 2.7 made me realize that
> they don't interoperate with other classes in a natural way and so
> nullify their a
Hello,
As a leap of faith, I have added Stephen Hansen's x86 Leopard buildbot
to the list of stable bots. Stephen has been very proactive in
diagnosing and fixing issues (thank you!).
Antoine.
___
Python-Dev mailing list
Python-Dev@python.org
http://
On Fri, 29 Oct 2010 02:55:55 -0400
Glyph Lefkowitz wrote:
>
> Let's say that 20% of the code on PyPI is just junk;
> it's unfair to expect 100% of all code ever to get ported. But, still:
> with this back-of-the-envelope estimate of the rate of porting, it will
> take over 50 years before a deci
On Fri, 29 Oct 2010 16:41:19 -
exar...@twistedmatrix.com wrote:
>
> Brett is speaking for himself here (and he never claimed otherwise!).
> However, decisions about where to allow the use of the "Python"
> trademark are made by the Python Software Foundation.
The point is not to allow the u
On Fri, 29 Oct 2010 15:54:19 -0400
Barry Warsaw wrote:
> Another quick thought. What would people think about regular timed releases
> if python 2.7?
> This is probably more a question for Benjamin but doing sonmight
> provide better predictability and "customer service" to our users. I
> might l
On Sat, 30 Oct 2010 02:13:01 +0200 (CEST)
brett.cannon wrote:
> Author: brett.cannon
> Date: Sat Oct 30 02:13:00 2010
> New Revision: 85960
>
> Log:
> Silence some ResourceWarning in test_mailbox by using file context managers.
Unfortunately, these file-like objects don't support the context
man
3001 - 3100 of 4909 matches
Mail list logo
