Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after they commit some changes (or at least
on a regular,
Am 04.08.2010 18:45, schrieb exar...@twistedmatrix.com:
How hard is it to look at a web page?
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. So if
Am 04.08.2010 18:21, schrieb David Stanek:
On Wed, Aug 4, 2010 at 11:53 AM, Georg Brandl g.bra...@gmx.net 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
Am 04.08.2010 17:53, schrieb Georg Brandl:
Am 04.08.2010 17:15, schrieb exar...@twistedmatrix.com:
On 02:51 pm, ba...@python.org wrote:
On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:
I think the issue is that many core developers don't have the reflex
to check buildbot state after
Am 04.08.2010 20:25, schrieb Barry Warsaw:
On Aug 04, 2010, at 01:56 PM, Steve Holden wrote:
But I see rules being established (there's a language moratorium: no
changes!, no release should be made unless the buildbots are *all*
green) and then ignored apparently on a whim. This doesn't give
Am 04.08.2010 19:56, schrieb Steve Holden:
This whole discussion seems to make it clear that the release manager
procedures are still ill-defined in certain areas.
If you mean to imply that a release manager should care for the stability
of their branch also in between of releases -- I'd love
Am 05.08.2010 01:26, schrieb Barry Warsaw:
On Aug 04, 2010, at 06:39 PM, Steve Holden wrote:
I'll see if I can get God to extend it for you.
No need to involve the supernatural Steve! Just approve that PSF grant I
submitted so I can finish my (Python powered of course!) clone army.
*Now*
Am 17.08.2010 02:52, schrieb benjamin.peterson:
Author: benjamin.peterson
Date: Tue Aug 17 02:52:52 2010
New Revision: 84124
Log:
add support for abstract class and static methods #5867
Modified:
python/branches/py3k/Doc/library/abc.rst
python/branches/py3k/Lib/abc.py
Am 18.08.2010 20:59, schrieb Martin v. Löwis:
Am 18.08.2010 17:11, schrieb Michael Foord:
Could (and should) the online Python 3.1 docs be updated to show Python
2.7 as stable?
I think the answer is no, it could not.
How many old documentation sets would you want to go through, and
Am 19.08.2010 15:32, schrieb Nick Coghlan:
On Thu, Aug 19, 2010 at 9:55 PM, Éric Araujo mer...@netwok.org wrote:
Thanks for the replies.
The dev FAQ is clear about regular use, it tells about the
svnmerge-commit-message too, and people in #python-dev have told me that
the merge order is py3k
Am 21.08.2010 04:54, schrieb benjamin.peterson:
Author: benjamin.peterson
Date: Sat Aug 21 04:54:44 2010
New Revision: 84229
Log:
alias macintosh to mac_roman #843590
Modified:
python/branches/py3k/Doc/library/codecs.rst
python/branches/py3k/Lib/encodings/aliases.py
Am 21.08.2010 13:00, schrieb M.-A. Lemburg:
Georg Brandl wrote:
Am 21.08.2010 04:54, schrieb benjamin.peterson:
Author: benjamin.peterson
Date: Sat Aug 21 04:54:44 2010
New Revision: 84229
Log:
alias macintosh to mac_roman #843590
Modified:
python/branches/py3k/Doc/library/codecs.rst
Am 25.08.2010 17:32, schrieb Éric Araujo:
The question really is whether there is any chance that they will get
released, in some form. There won't be further binary releases (at least
not from python.org), so there definitely won't be a CHM release.
I think that the most important release
That title isn't better though, since it doesn't cover the using/cmdline
document which deals with command line options, environment variables
and the like.
I agree that Using Python is not very descriptive though.
Georg
Am 01.09.2010 10:57, schrieb raymond.hettinger:
Author: raymond.hettinger
Am 01.09.2010 23:43, schrieb Nick Coghlan:
On Thu, Sep 2, 2010 at 7:25 AM, Georg Brandl g.bra...@gmx.net wrote:
That title isn't better though, since it doesn't cover the using/cmdline
document which deals with command line options, environment variables
and the like.
I agree that Using
Hi Victor,
1. This function and PyUnicode_strcat are missing documentation.
2. Are you sure they need to be public APIs? What are they going to
be used for? (I'm not sure myself, but I think we usually have a
short notice here when new C APIs are added.)
Georg
Am 02.09.2010 01:43,
Am 03.09.2010 01:26, schrieb Victor Stinner:
Hi,
Le jeudi 02 septembre 2010 11:13:22, vous avez écrit :
1. This function and PyUnicode_strcat are missing documentation.
It's Py_UNICODE_strcat(), not PyUnicode_strcat(). But yes,
Py_UNICODE_strcat()
is not documented. But I didn't found
This is to let you all know that PEP 3149 is accepted.
Benjamin and I decided that on the basis that
* strong precedent is set with PEP 3147
* it is not mutually exclusive with PEP 384; should PEP 384 become
widely accepted, its use can fade out again
* it is a strictly optional feature
Barry
Please add a versionadded tag.
Georg
Am 03.09.2010 18:23, schrieb victor.stinner:
Author: victor.stinner
Date: Fri Sep 3 18:23:29 2010
New Revision: 84456
Log:
Document PyUnicode_AsUnicodeCopy()
Modified:
python/branches/py3k/Doc/c-api/unicode.rst
Modified:
Am 03.09.2010 18:24, schrieb Victor Stinner:
Other than that, ok, let's have them.
Ok.
r84455 renames PyUnicode_strdup() to PyUnicode_AsUnicodeCopy(), and r84456
document it:
--
... cfunction:: Py_UNICODE* PyUnicode_AsUnicodeCopy(PyObject *unicode)
Create a copy of a
Am 03.09.2010 13:44, schrieb Nick Coghlan:
On Fri, Sep 3, 2010 at 9:19 PM, Amaury Forgeot d'Arc amaur...@gmail.com
wrote:
2010/9/3 Nick Coghlan ncogh...@gmail.com:
Due to the Unicode API discussion, I happened to be looking at the C
API docs at
Hi,
I'm not sure what the arrangement for the What's New in Python 3.2 document
is; especially if either Andrew or Raymond still feel in charge for it.
For this weekend's 3.2a2, it would be rather nice to have some more coverage
of changes in the document, since it is the main thing people will
Am 04.09.2010 01:40, schrieb Victor Stinner:
Le samedi 04 septembre 2010 00:52:38, Georg Brandl a écrit :
For this weekend's 3.2a2, it would be rather nice to have some more
coverage of changes in the document, since it is the main thing people
will look at when determining whether to download
Am 04.09.2010 01:26, schrieb Raymond Hettinger:
On Sep 3, 2010, at 3:52 PM, Georg Brandl wrote:
Hi,
I'm not sure what the arrangement for the What's New in Python 3.2 document
is; especially if either Andrew or Raymond still feel in charge for it.
I'm already working on it.
Thanks
Am 04.09.2010 12:06, schrieb Antoine Pitrou:
On Sat, 04 Sep 2010 11:42:08 +0200
Éric Araujo mer...@netwok.org wrote:
What about adding an intermediate namespace called cache, so that the
new
operations are available like this:
print get_phone_number.cache.hits
Am 05.09.2010 13:18, schrieb Antoine Pitrou:
On Sun, 5 Sep 2010 02:27:25 +0200 (CEST)
raymond.hettinger python-check...@python.org wrote:
+
+The common directory is pyshared and the file names are made distinct by
+identifying the Python implementation (such as CPython, PyPy, Jython,
Am 05.09.2010 19:22, schrieb Martin v. Löwis:
I know the PEP is accepted, but I would still like to see some
changes/clarifications.
1. What is the effect of this PEP on Windows? Is this a Linux-only
feature? If not, who is going to provide the changes for Windows?
(More specifically:
/3.2/
Please consider trying Python 3.2 with your code and reporting any bugs
you may notice to:
http://bugs.python.org/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-BEGIN PGP SIGNATURE-
Version: GnuPG
Am 07.09.2010 09:21, schrieb Dirkjan Ochtman:
On Tue, Sep 7, 2010 at 01:04, Antoine Pitrou solip...@pitrou.net wrote:
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)?
IIRC you just need
Am 07.09.2010 10:29, schrieb Dirkjan Ochtman:
On Tue, Sep 7, 2010 at 10:11, Georg Brandl g.bra...@gmx.net wrote:
To be a bit more precise, having a public key on file for SVN commits is
enough,
Not exactly, hg uses a separate keystore, so it might not have some of
the newer keys.
Oh ok, I
Hey #python-dev,
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
Am 10.09.2010 14:41, schrieb Nick Coghlan:
On Fri, Sep 10, 2010 at 5:06 PM, Eli Bendersky eli...@gmail.com wrote:
Nick, did you know that dis.show_code is neither exported by default from
the dis module, nor it's documented in its help() or .rst documentation?
Neither is code_info(), which is
Victor changed this from return NULL to goto fail in r84730, claiming
that it would fix a reference leak. Is the leak somewhere else then?
Georg
Am 12.09.2010 18:40, schrieb benjamin.peterson:
Author: benjamin.peterson
Date: Sun Sep 12 18:40:53 2010
New Revision: 84744
Log:
use return
Am 15.09.2010 20:32, schrieb Barry Warsaw:
On Sep 15, 2010, at 11:11 AM, 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
Maybe you want to mention *who* warns?
Georg
Am 13.09.2010 10:20, schrieb florent.xicluna:
Author: florent.xicluna
Date: Mon Sep 13 10:20:19 2010
New Revision: 84771
Log:
Silence warning about 1/0
Modified:
python/branches/release27-maint/Lib/test/test_io.py
Modified:
That reminds me of the undocumented re.Scanner -- which is meant to do
exactly this. Wouldn't it be about time to document or remove it?
Georg
Am 16.09.2010 14:02, schrieb raymond.hettinger:
Author: raymond.hettinger
Date: Thu Sep 16 14:02:17 2010
New Revision: 84847
Log:
Add tokenizer
Am 21.09.2010 01:42, schrieb Éric Araujo:
Hello
+ NOTE: If you are thinking of defining your own levels, please see
the section
+ on :ref:`custom-levels`.
I think those instances of upper-case-as-markup should either be real
reST note/warning/etc. directives or plain English (that
Am 21.09.2010 01:02, schrieb benjamin.peterson:
Author: benjamin.peterson
Date: Tue Sep 21 01:02:10 2010
New Revision: 84931
Log:
add column offset to all syntax errors
Modified: python/branches/py3k/Misc/NEWS
==
Am 23.09.2010 07:32, schrieb Jack Diederich:
On Wed, Sep 22, 2010 at 11:46 PM, Raymond Hettinger
raymond.hettin...@gmail.com wrote:
On Sep 22, 2010, at 6:24 PM, R. David Murray wrote:
On Wed, 22 Sep 2010 19:18:35 -0400, Terry Reedy tjre...@udel.edu wrote:
deputed tracker authority/ies. Not
That's right. It is true that it isn't branch-specific information,
and that does cause a little bit of irritation for me too, but neither
is Misc/developers.txt or Misc/maintainers.rst.
Of course, we might consider a separate HG repository (I'm all in favor
of many small repos, instead of a
Am 23.09.2010 04:35, schrieb Steven D'Aprano:
On Thu, 23 Sep 2010 10:18:39 am Tim Peters wrote:
Yikes - Mark has done terrific work in some very demanding areas,
I'd hate to see him feel unwelcome. So that's my advice: find a
way to smooth this over. You're welcome ;-)
I'd like to
Am 23.09.2010 09:18, schrieb Martin v. Löwis:
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 have a tracker
BD. Brett and
Am 23.09.2010 16:35, schrieb Barry Warsaw:
On Sep 23, 2010, at 10:06 AM, Jesse Noller wrote:
-1 on wiki; wikis are where good information goes off to die.
Well, *all* documentation requires vigilance to remain relevant and current.
I'm sure you don't think the Python wiki is useless, right?
Am 23.09.2010 16:47, schrieb Guido van Rossum:
On Thu, Sep 23, 2010 at 7:35 AM, Barry Warsaw ba...@python.org wrote:
On Sep 23, 2010, at 10:06 AM, Jesse Noller wrote:
-1 on wiki; wikis are where good information goes off to die.
Well, *all* documentation requires vigilance to remain relevant
Am 23.09.2010 16:41, schrieb Barry Warsaw:
On Sep 23, 2010, at 09:06 AM, Benjamin Peterson wrote:
Are any of our docs subject to release schedules?
I guess what I'm concerned about is this scenario:
You're a developer who has the source code to Python 3.1. You read the
in-tree docs to
Am 23.09.2010 19:22, schrieb Terry Reedy:
Asking every now and then is this still an issue, or setting
the version number, doesn't really advance the issue.
Numerous issues have been advanced by the questions I and Mark have
asked. Some were legitimately closed as out of date (the bug
Am 23.09.2010 22:51, schrieb Éric Araujo:
Le 23/09/2010 19:22, Terry Reedy a écrit :
As of just now, if you were to wonder What (security) bugs are open for
2.5 and search on open 2.5 issues, you would get a list of 44 issues.
It is only 44 instead of hundreds because of the work I and Mark
Am 23.09.2010 22:25, schrieb anatoly techtonik:
On Thu, Sep 23, 2010 at 6:57 PM, Barry Warsaw ba...@python.org wrote:
I certainly agree with that. So, how can we solve those problems? Radomir
has shell access now so perhaps we can ask him to make the Python wiki theme
more visually
Is it me, or is the open and closed count confusing to anyone else?
I.e., shouldn't the total delta equal the sum of the open delta and
the closed delta?
Georg
Am 24.09.2010 20:00, schrieb Brett Cannon:
I think every week where more bugs are closed than opened should be
celebrated! =) Thanks
, 2010 at 12:57, Georg Brandl g.bra...@gmx.net wrote:
Is it me, or is the open and closed count confusing to anyone else?
I.e., shouldn't the total delta equal the sum of the open delta and
the closed delta?
The total delta is a complete count of bugs, while the open and closed
deltas can apply
Am 25.09.2010 03:45, schrieb Brett Cannon:
On Fri, Sep 24, 2010 at 13:04, Georg Brandl g.bra...@gmx.net wrote:
So by opening and closing a bug 5 times within a week, the open and
close counters both go up by 5? That would be stupid.
No, as in a bug was re-opened last week and then closed
Am 25.09.2010 14:10, schrieb Martin v. Löwis:
Guess the only way to settle this is look at the code, but I don't
care enough to bother. =)
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 less open bugs
Am 25.09.2010 15:15, schrieb anatoly techtonik:
Hi,
I wonder if situation with relative imports in packages is improved in
Python 3k or we are still doomed to a chain of hacks?
My user story:
I am currently debugging project, which consists of many modules in one
package.
Each module
Am 25.09.2010 15:15, schrieb David Stanek:
On Sat, Sep 25, 2010 at 8:22 AM, anatoly techtonik techto...@gmail.com
wrote:
For me a major annoyance is the empty page with two links on wiki.python.org
While it allows to tell new people that there is also a Jython wiki,
my vision that it should
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 less open bugs
at the end of the week than at the start
Am 25.09.2010 21:12, schrieb Paul Boddie:
Georg Brandl wrote:
Am 23.09.2010 22:25, schrieb anatoly techtonik:
On Thu, Sep 23, 2010 at 6:57 PM, Barry Warsaw barry at python.org wrote:
I certainly agree with that. So, how can we solve those problems?
Radomir has shell access now so
Am 25.09.2010 23:41, schrieb Martin v. Löwis:
I guess a better example would be
old:
open #1 #2
closed #3
new:
open #1
closed #2 #3 #4 #5
which results in +2 for open (since #4 and #5 were opened) and +3 for closed
(since #2, #4 and #5 were closed), however the total issue
Am 25.09.2010 23:43, schrieb Martin v. Löwis:
For me a major annoyance is the empty page with two links on
wiki.python.org
While it allows to tell new people that there is also a Jython wiki,
my vision that it should be instead be oriented on existing
contributors immediately providing
Am 26.09.2010 00:16, schrieb Martin v. Löwis:
Redirect wiki.python.org to the Python wiki front page, and put the Jython
wiki somewhere on its own (whether it's wiki.jython.org or not).
But that can't work: then off-site links into either wiki break.
Why -- they can be redirected easily.
Am 26.09.2010 14:59, schrieb Martin v. Löwis:
Am 26.09.2010 13:58, schrieb Nick Coghlan:
On Sun, Sep 26, 2010 at 8:16 AM, Martin v. Löwis mar...@v.loewis.de
wrote:
But that can't work: then off-site links into either wiki break.
Georg isn't suggesting a general structural change, just a
Am 26.09.2010 12:55, schrieb Dirkjan Ochtman:
Hi all,
I've recently been working on the conversion more (since my thesis got
finished). I finally wrote the script that splits the release branches
from the feature branches, so that we can include the former in the
main repository and keep
Am 27.09.2010 07:32, schrieb kristjan.jonsson:
Author: kristjan.jonsson
Date: Mon Sep 27 07:32:54 2010
New Revision: 85028
Log:
issue 9910
Add a Py_SetPath api to override magic path computations when starting up
python.
Modified:
python/branches/py3k/Doc/c-api/init.rst
Am 27.09.2010 22:33, schrieb P.J. Eby:
At 12:36 PM 9/27/2010 -0700, Brett Cannon wrote:
All fixed.
Nope. I mean, sure, I checked in fixed PEP sources several hours
ago, but python.org still doesn't show PEP , or the updated
version of PEP 333.
It does now, for me, so I assume
Am 29.09.2010 09:03, schrieb Dirkjan Ochtman:
On Wed, Sep 29, 2010 at 03:13, Steve Holden st...@holdenweb.com wrote:
I see that Atlassian have just taken over BitBucket, the Mercurial
hosting company. IIRC Atlassian offered to host our issue tracking on
JIRA, but in the end we decided to eat
Am 29.09.2010 20:49, schrieb Guido van Rossum:
Unfortunately taking the average patch posted to the tracker and
importing it in Rietveld is very iffy -- it's very hard to find the
right branch+rev needed to be able to apply the patch correctly -- not
to mention that there are so many
Am 01.10.2010 03:13, schrieb Antoine Pitrou:
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?
Yes, I noticed it in my cronjob email. It seems latex has a problem with
c-api.tex; I'll have a
Am 01.10.2010 01:50, schrieb Martin v. Löwis:
Amaury just filed issue #1 yesterday; as counting started
with 1000, we are now into 9000 roundup issues.
So, nitpickly, it would be 9001. But of course, we're already at
10003 anyway :)
I have become quite fond of roundup over the years, and
Am 30.09.2010 10:22, schrieb Dirkjan Ochtman:
On Wed, Sep 29, 2010 at 20:32, Guido van Rossum gu...@python.org 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
Am 02.10.2010 00:06, schrieb Barry Warsaw:
Let's say I build the foo module, which has an _foo extension for both the
3.2m and 3.2dmu builds. Everything gets installed correctly, and you'll see:
lib/python3.2/site-packages/foo-...egg/_foo.cpython-32m.so
Am 08.10.2010 09:05, schrieb Tarek Ziadé:
Hello,
In the Distutils2 project, we'll have quite a few scripts that can be
called via -m
$ python -m distutils2.depgraph : shows a dependency graph
$ python -m distutils2.install : installs a project
$ python -m distutils2.run command : runs a
Am 08.10.2010 10:50, schrieb Chris Withers:
Hi All,
The new explicit relative import syntax is great.
I wanted to relatively import a module.
import .mymoduleinmypackage
and got a SyntaxError in Python 2.6.
I guess I need to do:
from . import mymoduleinmypackage
but it
Am 08.10.2010 14:02, schrieb Fred Drake:
Georg:
What happened to python setup.py action? Or is this a step towards
not requiring setup.py at all?
I'm in favor of add a top-level setup module that can be invoked using
python -m setup There will be three cases:
- d2 projects
Am 08.10.2010 16:26, schrieb Barry Warsaw:
- 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
command-not-found on Ubuntu doesn't
://docs.python.org/3.2/
Please consider trying Python 3.2 with your code and reporting any bugs
you may notice to:
http://bugs.python.org/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-BEGIN PGP SIGNATURE
Am 13.10.2010 22:55, schrieb Martin v. Löwis:
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.
I would also like to ask release managers to take the
stable
Am 14.10.2010 18:55, schrieb Antoine Pitrou:
On Thu, 14 Oct 2010 08:07:46 +0200
Georg Brandl g.bra...@gmx.net 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
Am 16.10.2010 03:04, schrieb barry.warsaw:
Author: barry.warsaw
Date: Sat Oct 16 03:04:07 2010
New Revision: 85559
Log:
First (uncontroversial) part of issue 9807.
* Expose the build flags to Python as sys.abiflags
* Shared library libpythonX.Yabiflags.so
* python-config --abiflags
*
Am 18.10.2010 20:11, schrieb Barry Warsaw:
On Oct 18, 2010, at 04:04 PM, Éric Araujo wrote:
Raymond Hettinger noticed on the tracker that there are different
interpretations of the “accepted” resolution:
Traditionally it denotes an approved patch, not a agreement that the
bug is valid.
Am 18.10.2010 21:04, schrieb Michael Foord:
On 18/10/2010 19:18, Georg Brandl wrote:
Am 18.10.2010 20:11, schrieb Barry Warsaw:
On Oct 18, 2010, at 04:04 PM, Éric Araujo wrote:
Raymond Hettinger noticed on the tracker that there are different
interpretations of the “accepted” resolution
Am 18.10.2010 21:28, schrieb Michael Foord:
On 18/10/2010 20:24, Georg Brandl wrote:
Am 18.10.2010 21:04, schrieb Michael Foord:
On 18/10/2010 19:18, Georg Brandl wrote:
Am 18.10.2010 20:11, schrieb Barry Warsaw:
On Oct 18, 2010, at 04:04 PM, Éric Araujo wrote:
Raymond Hettinger
Am 19.10.2010 16:12, schrieb Barry Warsaw:
On Oct 19, 2010, at 03:53 AM, Victor Stinner wrote:
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that
Am 19.10.2010 17:26, schrieb vinay.sajip:
Author: vinay.sajip
Date: Tue Oct 19 17:26:24 2010
New Revision: 85724
Log:
logging: Added _logRecordClass, getLogRecordClass, setLogRecordClass to
increase flexibility of LogRecord creation.
Will this be documented?
Georg
--
Thus spake the
Am 22.10.2010 09:36, schrieb Dirkjan Ochtman:
On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson benja...@python.org wrote:
In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a
tentative release schedule:
November 13th - RC1
November 27th - RC2
December 11th - Final
The
Am 22.10.2010 11:41, schrieb Dirkjan Ochtman:
On Fri, Oct 22, 2010 at 11:06, Georg Brandl g.bra...@gmx.net wrote:
If everything goes as planned, there won't be many commits between RC2 and
final, so it should be fine. The svn repos won't be removed anyway, so
making a release from them
Am 19.10.2010 17:24, schrieb P.J. Eby:
At 08:03 AM 10/18/2010 +1000, Nick Coghlan wrote:
I'm a little dubious about exposing these officially. They're mainly a
hack to get some parts of the standard library working (e.g. runpy) in
the absence of full PEP 302 support in the imp module, not really
Am 23.10.2010 19:08, schrieb Antoine Pitrou:
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.
I'll
Am 25.10.2010 19:37, schrieb victor.stinner:
Author: victor.stinner
Date: Mon Oct 25 19:37:18 2010
New Revision: 85838
Log:
update gitignore
Added:
python/branches/py3k/.gitignore
This looks more like Add gitignore. Do we really want to check in
ignore files for every possible
Am 26.10.2010 19:53, schrieb Brett Cannon:
Can whomever has edit access to the Python Google Calendar add this?
Done.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall
Am 27.10.2010 09:25, schrieb anatoly techtonik:
On Tue, Oct 26, 2010 at 3:51 PM, Barry Warsaw ba...@python.org wrote:
On Oct 26, 2010, at 09:19 PM, Nick Coghlan wrote:
On Tue, Oct 26, 2010 at 5:31 PM, Georg Brandl g.bra...@gmx.net wrote:
This looks more like Add gitignore. Do we really want
Am 28.10.2010 06:13, schrieb Daniel Stutzbach:
2010/10/27 Kristján Valur Jónsson krist...@ccpgames.com
mailto:krist...@ccpgames.com
Firstly, the ease of integrating changes. It would be possible to port
those bugfixes that release-27 gets, and also backport selected things
from
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 beast is to analyze its
memory-related behaviour from an external POV
Am 28.10.2010 18:07, schrieb l...@rmi.net:
Kristj?n Valur J?nsson krist...@ccpgames.com writes:
James Y Knight said:
The python community has already decided many times over that Python2 is
dead
and Python3 is the future
But the patient is very much alive and kicking, no matter what the
Am 30.10.2010 12:12, schrieb Antoine Pitrou:
On Sat, 30 Oct 2010 02:13:01 +0200 (CEST)
brett.cannon python-check...@python.org 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.
Am 03.11.2010 03:35, schrieb Antoine Pitrou:
On Tue, 2 Nov 2010 19:57:48 -0700
Brett Cannon br...@python.org wrote:
How could we have split the module into a package in a way that matched the
API, whilst still retaining backwards compatibility with the old API? We
had
no choice but to
Am 06.11.2010 05:44, schrieb Ezio Melotti:
Hi,
On 05/11/2010 19.08, Python tracker wrote:
ACTIVITY SUMMARY (2010-10-29 - 2010-11-05)
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
Am 07.11.2010 12:50, schrieb Nick Coghlan:
On Sun, Nov 7, 2010 at 9:24 PM, Trent Nelson tr...@snakebite.org wrote:
1. Set up standard build slaves on all the platforms, but put something in
place that allowed committers to ssh/mstsc in to said slaves when things go
wrong in order to aid with
Am 08.11.2010 01:13, schrieb Martin v. Löwis:
I've spent a good bit of time on that, and left all the instructions in
the buildbot master config. I also adapted buildbot's hg hook to our
situation (e.g. to send a change to multiple masters, as required for
the community buildbots), so it
Am 08.11.2010 17:02, schrieb Éric Araujo:
Hi Nick,
If there is no enormous difficulty in maintaining compatibility, I think
the usual deprecation process should be followed. We don’t know who is
using pydoc as a library, so let’s play safe and not risk breaking their
code (especially
Am 14.11.2010 13:39, schrieb Nick Coghlan:
On Sun, Nov 14, 2010 at 8:20 PM, Martin v. Löwis mar...@v.loewis.de wrote:
See
http://hg.python.org/hooks/
You should have push permissions to that repository.
I suspect my hg-fu is inadequate to at this point - I get an 'access
to repository
Am 14.11.2010 19:35, schrieb Antoine Pitrou:
On Sun, 14 Nov 2010 19:27:22 +0100
Martin v. Löwis mar...@v.loewis.de wrote:
I suspect my hg-fu is inadequate to at this point - I get an 'access
to repository hg.python.org/hooks not permitted' error when I try to
push the modified file to
801 - 900 of 1517 matches
Mail list logo
