Benjamin Peterson schrieb:
Hi,
What is the policy regarding nosy lists? Is it appropriate it add people
to it besides oneself? As I cannot assign items, I'm sometimes tempted
to add someone relevant to the list. (ie Should I add Georg to
documentation related issues?)
In my case, yes
Nick Coghlan schrieb:
Facundo Batista wrote:
First two definitions of resolve from the American Heritage dict:
1. To make a firm decision about.
2. To cause (a person) to reach a decision.
I think it applies quite well.
It only tells you that a resolution was reached, not what that
[EMAIL PROTECTED] schrieb:
This message has been popping up in the buildbot mails for several days:
Conflict detected in commontex/boilerplate.tex. Doc build skipped.
I have no idea what it means. I don't see it within the core distribution.
Can someone take a look at this?
Neal
Eric Smith schrieb:
Guido van Rossum wrote:
I wonder if, in order to change the behavior of various built-in
functions, it wouldn't be easier to be able to write
from future_builtins import oct, hex # and who knows what else
This makes sense to me, especially if we have a 2to3 fixer
Scott Dial schrieb:
Barry Warsaw wrote:
Alterntaively, I guess you could just suggest that people check the
buildbot page for their platforms before downloading
Yes, good idea. I'm only going to cut source tarballs for the alphas.
I apologize for having doubt in your plan, and I
Neal Becker schrieb:
http://docs.python.org/dev/download.html
I want a pdf. The above link says:
To download an archive containing all the documents for this version of
Python in one of various formats, follow one of links in this table.
But there are no links.
Unfortunately, we
Barry Warsaw schrieb:
PEP 101 is sorely out of date, especially with regards to updating web
content and the Python documentation. I think I now know how to
update the python.org web site, but the new Python documentation
format is still a mystery to me. If someone would like to help update
The Callable abc has a __contains__ but no __call__ method.
I'd fix this, but am unsure which args it should get.
Georg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Steve Holden schrieb:
Paul Moore wrote:
On 04/03/2008, Nick Coghlan [EMAIL PROTECTED] wrote:
Do we need a new appendix to the tutorial which goes into detail about
the CPython interpreter's command line options, environment variables
and details on what can be executed?
There is a Python
Adam Olsen schrieb:
I don't pretend to be speaking for anyone else, but I'd be surprised
if I were unique.wink
Your experiences *shouldn't* be unique, but I'm afraid they might be.
Another example is the use of BNF, which although dominant in its
field, it provides a steep learning curve
Nick Coghlan schrieb:
Georg Brandl wrote:
Steve Holden schrieb:
Paul Moore wrote:
On 04/03/2008, Nick Coghlan [EMAIL PROTECTED] wrote:
Do we need a new appendix to the tutorial which goes into detail about
the CPython interpreter's command line options, environment variables
and details
implemented
as a special case), and Documentation and Sphinx to Georg Brandl.
Thanks Martin!
Georg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
While fixing the broken links in the docs, I saw that the link to
http://www.pythonlabs.com/logos.html in the BEOPEN PYTHON OPEN SOURCE
LICENSE AGREEMENT VERSION 1 is broken.
What to do about that?
Georg
___
Python-Dev mailing list
Guido van Rossum schrieb:
But perhaps the best feature is hot lists -- arbitrary, ordered,
groupings of selected bugs. Each bug can be assigned to as many hot
lists as you want. Seeing the list of all bugs in a particular hot
list is one click away. We use this for overlaying project
Brett Cannon schrieb:
I have been writing up the initial docs for importlib and four things struck
me:
1. Why is three space indents the preferred indentation level?
As said, it matches directive content with directive headers nicely.
Ben's solution is nice as well, but now that we have
Brett Cannon schrieb:
3. Are brackets for optional arguments (e.g. ``def fxn(a [, b=None [,
c=None]])``) really necessary when default argument values are
present? And do we really need to nest the brackets when it is obvious
that having on optional argument means the rest are optional as
Brett Cannon schrieb:
4. The var directive is not working even though the docs list it as a
valid directive; so is it still valid and something is broken, or the
docs need to be updated?
(First, you're confusing directive and role which led to some confusion
on Benjamin's part.)
Where is
(re #5066)
Is that documentation maintained in some way? Shouldn't it be merged
into the main docs?
Georg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Raymond Hettinger schrieb:
[Martin]
I would fear that than 3.1 gets the same fate as 3.0. In May, we will
all think what piece of junk was that 3.1 release, let's put it to
history, and replace it with 3.2. By then, users will wonder if there
is ever a 3.x release that is any good.
I
Guido van Rossum schrieb:
Frankly, I don't really believe the users for whom those rules were
created are using 3.0 yet. Instead, I expect there to be two types of
users: people in the educational business who don't have a lot of
bridges to burn and are eager to use the new features; and
gl...@divmod.com schrieb:
On 01:00 am, greg.ew...@canterbury.ac.nz wrote:
Guido van Rossum wrote:
We already have yield expressions and they mean something else...
They don't have a * in them, though, and I don't
think the existing meaning of yield as an expression
would carry over into the
Daniel (ajax) Diniz schrieb:
Over-spammig:
Sorry, Georg! I only noticed all issues in the Documentation
component are auto-assigned to you today. This meant dozens of unasked
for assignments :-/
That's okay, I'll go through them at the weekend and just unassign what
I won't manage to do.
Raymond Hettinger schrieb:
[Greg Ewing]
I've discovered something slightly misleading in the docs
for PyObject_IsInstance:
When testing if B is a subclass of A, if A is B, PyObject_IsSubclass
returns true. If A and B are different objects, B's __bases__
attribute is searched...
This
Benjamin Peterson schrieb:
On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se wrote:
Didn't a test fail because of this? seems the underlying issue is that this
part of the stdlib didn't have enough test coverage. It seems that having
very good/improving test coverage like is
Benjamin Peterson schrieb:
On Tue, Feb 17, 2009 at 3:02 PM, Georg Brandl g.bra...@gmx.net wrote:
Benjamin Peterson schrieb:
On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni pedro...@openend.se
wrote:
Didn't a test fail because of this? seems the underlying issue is that this
part
Stephen J. Turnbull schrieb:
FWIW, Google Docs is almost there. Working with Brett et al on early
drafts of PEP 0374 was easy and pleasant, and Google Docs gives
control of access to the document to the editor, not the Subversion
admin. The ability to make comments that are not visible to
Antoine Pitrou schrieb:
Benjamin Peterson benjamin at python.org writes:
As we prepare to merge the io-c branch, the question has come up [1]
about the original Python implementation. Should it just be deleted in
favor C version? The wish to maintain the two implementations together
has
Guido van Rossum schrieb:
I think the better syntax would be to add site:mail.python.org to the
query, but you're right, that doesn't seem to find recent messages.
Maybe the absence of a robots.txt file on mail.python.org could be a
partial explanation?
Doesn't the absence of a robots.txt
Benjamin Peterson schrieb:
2009/3/1 Armin Ronacher armin.ronac...@active-4.com:
Hi everybody,
PEP 372 was modified so that it provides a simpler API (only the dict API
to be exact) and it was decided to start with a Python-only implementation
and replace it with a C version later if
James Y Knight schrieb:
On Mar 4, 2009, at 9:56 AM, Chris Withers wrote:
Vaibhav Mallya wrote:
We do have HTMLParser, but that doesn't handle malformed pages
well, and just isn't as nice as BeautifulSoup.
Interesting, given that BeautifulSoup is built on HTMLParser ;-)
I think
Chris Withers schrieb:
Hi All,
I found the very brief snippet on test-running at:
http://python.org/dev/faq/#how-to-test-a-patch
so thought I'd ask here:
- what's the canonical way to run all the tests?
Assuming UNIXy OSes: make test, or if you want to save a bit of time,
make
Benjamin Peterson schrieb:
2009/3/16 Brett Cannon br...@python.org:
At this point importlib is done for its public API for Python 3.1. That
means it's time to turn my attention to making sure the semantics of import
are well documented. But where to put all of the details? The language
Dirkjan Ochtman schrieb:
On 05/04/2009 12:27, Antoine Pitrou wrote:
There's also the issue of how we adapt the current workflow of svnmerging
between branches when we want to back- or forward-port stuff. In particular,
tracking of already done or blocked backports.
Right. The canonical way
Firephoenix schrieb:
Hello everyone
I'm a little confused by the recent changes to the generator system...
I basically agreed with renaming the next() method to __next__(), so as
to follow the naming of other similar methods (__iter__() etc.).
But I noticed then that all the other
Antoine Pitrou schrieb:
Georg Brandl g.brandl at gmx.net writes:
When commits with bad whitespace changes are rejected on push, this is a
pretty good incentive to run the pre-commit hook next time, so that you
don't have to re-do all the commits in that batch :)
Do you really have to re
Martin v. Löwis schrieb:
We could pre-record the list of allowed names in a hook, then have the
hook check that usernames include one of those names and an email
address (so people can still start using another email address).
What about commits from other people, e.g. pulled from a repo
Thomas Wouters schrieb:
Anyone able to look into this and fix it? Having all of the normal
entrypoints for documentation broken is rather inconvenient for users :-)
A rebuild should do the trick, I'll fix this ASAP.
Georg
___
Python-Dev mailing
Campbell Barton schrieb:
Hi, Just noticed the new Python 2.6.2 docs now dont have any reference to
* PyCFunction_New
* PyCFunction_NewEx
* PyCFunction_Check
* PyCFunction_Call
Ofcourse these are still in the source code but Im wondering if this
is intentional that these functions should
Hi,
I'd like to announce that there will be a Python Bug Day on April 23.
As always, this is a perfect opportunity to get involved in Python
development, or bring your own issues to attention, discuss them and
(hopefully) resolve them together with the core developers.
We will coordinate over
Hi,
I managed to screw up the date, so here it goes again:
I'd like to announce that there will be a Python Bug Day on April 25.
As always, this is a perfect opportunity to get involved in Python
development, or bring your own issues to attention, discuss them and
(hopefully) resolve them
Maciej Fijalkowski schrieb:
On Wed, Apr 15, 2009 at 1:10 PM, Georg Brandl ge...@python.org wrote:
Hi,
I managed to screw up the date, so here it goes again:
I'd like to announce that there will be a Python Bug Day on April 25.
Are you aware that this directly conflicts with TurboGears
Hi,
I'd like to remind everyoone that there will be a Python Bug Day on
April 25. As always, this is a perfect opportunity to get involved
in Python development, or bring your own issues to attention, discuss
them and (hopefully) resolve them together with the core developers.
We will
Tim Lesher schrieb:
Is there a reason that the PyEval_CallFunction() and
PyEval_CallMethod() convenience functions remain undocumented? (i.e.,
would a doc-and-test patch to correct this be rejected?)
I didn't see any mention of this coming up in python-dev before.
Also, despite its name,
Hi,
this is just a short notice that Mattias Brändström and I have finished a
patch to implement the previously discussed and mostly warmly welcomed
extension to with's syntax, allowing
with A() as a, B() as b:
to be written instead of
with A() as a:
with B() as b:
This syntax
Fredrik Johansson schrieb:
On Sat, May 2, 2009 at 9:01 PM, Georg Brandl g.bra...@gmx.net wrote:
Hi,
this is just a short notice that Mattias Brändström and I have finished a
patch to implement the previously discussed and mostly warmly welcomed
extension to with's syntax, allowing
Benjamin Peterson schrieb:
A while ago, Guido declared that all special method lookups on
new-style classes bypass __getattr__ and __getattribute__. This almost
completely consistent now, and I've been working on patching up a few
incorrect cases. I've know hit __enter__ and __exit__. The
Martin v. Löwis schrieb:
Header Files and Preprocessor Definitions
-
Applications shall only include the header file Python.h (before
including any system headers), or, optionally, include pyconfig.h, and
then Python.h.
What about structmember.h?
Neal Norwitz schrieb:
Has anyone run valgrind/purify and pychecker/pylint on the 3.1 code
recently? Both sets of tools should be used before the final release
so we can fix any obvious problems.
Do pychecker/pylint work on 3.x code?
Gerog
--
Thus spake the Lord: Thou shalt indent with
Benjamin Peterson schrieb:
2009/6/2 Guido van Rossum gu...@python.org:
Benjamin, what would be involved in removing it? I suppose there's the
module itself, some unit tests, and some docs. (I'm not asking you to
remove it yet -- but I'm asking to look into the consequences, so that
we can be
Antoine Pitrou schrieb:
Dirkjan Ochtman dirkjan at ochtman.nl writes:
http://www.python.org/dev/peps/pep-0385/
« [cloned branches] makes it easier to distinguish branches, at the expense of
requiring more disk space on the client. »
This is a bit misleading. Actually, by separating
Daniel Diniz schrieb:
anatoly techtonik wrote:
It is impossible to edit roundup keywords and this takes away the
flexibility in selecting bugs related to a module/function/test or
some other aspect of development. For example, I need to gather all
subprocess bugs in one query and things that
Frank Wierzbicki schrieb:
At PyCon, we discussed moving Jython's svn repository to Python's with
Martin von Löwis. I would think that Jython would live in Python's hg
repository in the same way as stackless and distutils. Has the
parallel project strategy been determined? Will they be
Frank Wierzbicki schrieb:
On Mon, Jun 8, 2009 at 11:32 AM, Dirkjan Ochtmandirk...@ochtman.nl wrote:
I'd say migrating to Python's svn doesn't make a whole lot of sense at
this point, but I'll leave that to Martin (since he has to do the
work). For the conversion, I can just as well take the
Benjamin Peterson schrieb:
Backwards compatibility seems to be an issue that arises a lot here. I
think we all have an idea of it is, but we need some hard place to
point to. So here's my attempt:
Yet another rather pointless bikeshed: if this becomes policy, maybe it
should get a PEP number
R. David Murray schrieb:
On Fri, 19 Jun 2009 at 14:15, Antoine Pitrou wrote:
Benjamin Peterson benjamin at python.org writes:
I mean that if you pass X and Y into a function and get Z in 2.6, then
you should be able to get Z from passing X and Y in 2.7 even if
there's a new argument that
Tobias C. Rittweiler schrieb:
Hi!
Has anyone added special syntax to allow writing numeric literals with
physical units? So you can write 12m + 34cm, and would get 12.34m.
My question is how would you modify the BNF the most sensible way to
allow for this? The above example is simple, but
Benjamin Peterson schrieb:
On behalf of the Python development team, I'm thrilled to announce the first
production release of Python 3.1.
Congrats!
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
Dirkjan Ochtman schrieb:
- Fifth, here's a list of things, off the top of my head, that still need
doing:
* Get agreement on branch strategy and branch processing (list of
branches + proposed handling at
http://hg.python.org/pymigr/file/tip/all-branches.txt) --- PLEASE
REVIEW
Do you
Martin v. Löwis schrieb:
We could add another value in the tuple that specifies the VCS:
('CPython', 'branches/release25-maint', '61464', 'svn'). I agree that
VCSs are not universally the same, but the concept of a revision is
universal.
Actually, I think that's not the case. For bzr, the
Martin v. Löwis schrieb:
It will handle it, for sure, but I think it would all go easier if we
could work with stricter subset branches (and leave the effective
cherrypicking for the occasional problem).
So I think the PEP should propose a workflow (or: merge flow) if you
think we would be
Hi all,
is the presence of None values in sys.modules considered an implementation
detail? If not, it should be documented what the None values mean to the
interpreter.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou
David Lyon schrieb:
On Fri, 24 Jul 2009 03:23:57 +0200, Christian Heimes li...@cheimes.de
wrote:
I'm sorry to inform you that a wxWindows based solution has zero change
to get into the Python standard library ever. We are not going to add
another GUI toolkit to the core distribution.
In
Neil Hodgson schrieb:
Martin v. Löwis:
Or don't you understand why that single unresolved item didn't manage
to revert the decision? Well, there are many unresolved items in
the Mercurial conversion, some much more stressful than the eol issue
(e.g. the branching discussion).
Then
Nick Coghlan schrieb:
Nick Coghlan wrote:
Benjamin Peterson wrote:
rant
If python-dev was more interested, we would have a policy for this. *cough*
/rant
PEP 5 isn't enough? (I'll grant that PEP could probably do with
mentioning the use of warnings.warn(DeprecationWarning) explicitly, but
Chris Withers schrieb:
Hi All,
Anyone know what's causing this failure?
test test___all__ failed -- Traceback (most recent call last):
File Lib/test/test___all__.py, line 106, in test_all
self.check_all(profile)
File Lib/test/test___all__.py, line 23, in check_all
On 10/28/11 22:05, florent.xicluna wrote:
http://hg.python.org/cpython/rev/6f56e81da8f6
changeset: 73171:6f56e81da8f6
branch: 3.2
parent: 73167:09d0510e1c50
user:Florent Xicluna florent.xicl...@gmail.com
date:Fri Oct 28 22:03:55 2011 +0200
summary:
I should be
Am 08.11.2011 21:30, schrieb brian.curtin:
http://hg.python.org/cpython/rev/60ae7979fec8
changeset: 73463:60ae7979fec8
user:Brian Curtin br...@python.org
date:Tue Nov 08 14:30:02 2011 -0600
summary:
Remove the old style [...] to denote optional args and show the defaults.
Am 11.11.2011 20:24, schrieb Eli Bendersky:
Hi,
Our Hg repo has some useful hooks on commit messages that allow to
specify which issue to notify for commits, and which issue to close.
AFAIU, it's currently documented only in the code of the hook
Am 12.11.2011 08:03, schrieb Stephen J. Turnbull:
Eli Bendersky writes:
special locale. It makes me wonder whether it's possible to have a
contradiction in the ordering, i.e. have a set of names that just
can't be sorted in any order acceptable by everyone.
Yes, it is. The examples
Am 29.11.2011 13:46, schrieb Petri Lehtinen:
Michael Foord wrote:
We tend to see 3.2 - 3.3 as a major version increment, but that's
just Python's terminology.
Even though (in the documentation) Python's version number components
are called major, minor, micro, releaselevel and serial, in
Am 01.12.2011 07:10, schrieb Raymond Hettinger:
When updating the documentation, please don't go overboard with warnings.
The docs need to be worded affirmatively -- say what a tool does and show how
to
use it correctly.
See http://docs.python.org/documenting/style.html#affirmative-tone
Am 04.12.2011 03:55, schrieb Terry Reedy:
On 12/3/2011 3:58 PM, Antoine Pitrou wrote:
On Sat, 3 Dec 2011 21:39:03 +0100
Antoine Pitrousolip...@pitrou.net wrote:
One primary example is the performance question:
Am 07.12.2011 02:23, schrieb Cameron Simpson:
On 30Nov2011 22:10, Raymond Hettinger raymond.hettin...@gmail.com wrote:
| When updating the documentation, please don't go overboard with warnings.
| The docs need to be worded affirmatively -- say what a tool does and show
how to use it
On 12/17/2011 11:33 AM, Matt Joiner wrote:
ಠ_ಠ
Would you please stop this? It may have been funny the first time, but
now it looks like pure trolling.
Georg
___
Python-Dev mailing list
Python-Dev@python.org
On 01/02/2012 03:41 PM, Antoine Pitrou wrote:
On Mon, 2 Jan 2012 14:44:49 +1000
Nick Coghlan ncogh...@gmail.com wrote:
He keeps leaving them out, I occasionally tell him they should always
be included (most recently this came up when we gave conflicting
advice to a patch contributor).
On 01/02/2012 04:47 PM, Christian Heimes wrote:
Am 01.01.2012 19:45, schrieb Terry Reedy:
On 1/1/2012 10:13 AM, Guido van Rossum wrote:
PS. Is the collision-generator used in the attack code open source?
As I posted before, Alexander Klink and Julian Wälde gave their project
email as
On 01/05/2012 09:45 PM, Barry Warsaw wrote:
On Jan 05, 2012, at 02:33 PM, David Malcolm wrote:
We have similar issues in RHEL, with the Python versions going much
further back (e.g. 2.3)
When backporting the fix to ancient python versions, I'm inclined to
turn the change *off* by default,
Caution, long review ahead.
On 01/13/2012 12:43 PM, nick.coghlan wrote:
http://hg.python.org/cpython/rev/d64ac9ab4cd0
changeset: 74356:d64ac9ab4cd0
user:Nick Coghlan ncogh...@gmail.com
date:Fri Jan 13 21:43:40 2012 +1000
summary:
Implement PEP 380 - 'yield from' (closes
On 01/14/2012 07:53 AM, Nick Coghlan wrote:
+PyAPI_FUNC(int) PyGen_FetchStopIterationValue(PyObject **);
Does this API need to be public? If yes, it needs to be documented.
Hmm, good point - that one needs a bit of thought, so I've put it on
the tracker: http://bugs.python.org/issue13783
Am 16.01.2012 17:28, schrieb Antoine Pitrou:
On Mon, 16 Jan 2012 11:17:42 -0500
Brett Cannon br...@python.org wrote:
Is the change to the pyc format big enough news to go into the release PEP?
Or should that just be a What's New topic?
What's New sounds enough to me. The change doesn't
Am 17.01.2012 19:02, schrieb Sandro Tosi:
I should have given more info, as I wanted the opposite result :)
file.next should not link to the next function but to the file.next
method. Because Sphinx does not differentiate between
meth/func/class/mod roles, :meth:`next` is not resolved to the
Am 18.01.2012 05:32, schrieb Terry Reedy:
On 1/17/2012 6:42 PM, Antoine Pitrou wrote:
On Tue, 17 Jan 2012 18:29:11 -0500
Terry Reedytjre...@udel.edu wrote:
To me, as I understand the proposal, the title is wrong. Our current
feather releases already are long-term support versions. They get
Am 18.01.2012 01:24, schrieb Jeff Hardy:
On Tue, Jan 17, 2012 at 3:50 PM, Ezio Melotti ezio.melo...@gmail.com wrote:
* What is the effect on PyPy/Jython/IronPython? Can they just skip the
feature releases and focus on the LTS ones?
At least for IronPython it's unlikely we'd be able track
Am 18.01.2012 00:50, schrieb Ezio Melotti:
Hi,
On 17/01/2012 22.34, Antoine Pitrou wrote:
[...]
Proposal
Under the proposed scheme, there would be two kinds of feature
versions (sometimes dubbed minor versions, for example 3.2 or 3.3):
normal feature versions and long-term
Am 18.01.2012 16:25, schrieb Stephen J. Turnbull:
Antoine Pitrou writes:
You claim people won't use stable releases because of not enough
alphas? That sounds completely unrelated.
Surely testing is related to user perceptions of stability. More
testing helps reduce bugs in released
Am 18.01.2012 18:56, schrieb Brett Cannon:
IOW we would have a language moratorium every 2 years (i.e. between LTS
releases) while switching to a 6 month release cycle for language/VM bugfixes
and full stdlib releases?
That is certainly a possibility (it's listed as an open issue in the PEP).
Am 19.01.2012 01:12, schrieb Steven D'Aprano:
One on-going complaint is that Python-Dev doesn't have the manpower or time
to
do everything that needs to be done. Bugs languish for months or years
because
nobody has the time to look at it. Will going to a more rapid release cycle
give
Am 20.01.2012 19:15, schrieb Guido van Rossum:
OTOH, if you change dictionary order and *that* breaks the application,
then
the bugs submitted to the application's tracker will be legitimate bugs
that
have to be fixed even if nothing else changed.
There are lots of things
Am 20.01.2012 00:54, schrieb Martin v. Löwis:
I can't help noticing that so far, worries about the workload came mostly
from
people who don't actually bear that load (this is no accusation!), while
those
that do are the proponents of the PEP...
Ok, so let me add then that I'm worried
Am 20.01.2012 21:08, schrieb Tim Golden:
On 20/01/2012 19:14, Georg Brandl wrote:
Am 20.01.2012 00:54, schrieb Martin v. Löwis:
I can't help noticing that so far, worries about the workload came mostly
from
people who don't actually bear that load (this is no accusation!), while
those
Am 20.01.2012 21:05, schrieb Ethan Furman:
Benjamin Peterson wrote:
2012/1/20 Ethan Furman et...@stoneleaf.us:
Summary:
Exception Chaining is cool, unless you are writing libraries that want to
transform from Exception X to Exception Y as the the previous exception
context is unnecessary,
Am 20.01.2012 20:05, schrieb Chris Withers:
On 14/01/2012 16:14, Sandro Tosi wrote:
Hello,
just a heads-up: documentation for 2.7 branch has been ported to use
sphinx 1.0, so now the same syntax can be used for 2.x and 3.x
patches, hopefully easying working on both python stacks.
That's
Am 23.01.2012 15:49, schrieb Łukasz Langa:
[graphics]
Pomyśl o środowisku naturalnym zanim wydrukujesz tę wiadomość!
Please consider the environment before printing out this e-mail.
Oh please?!
Georg
___
Python-Dev mailing list
Am 24.01.2012 18:58, schrieb brett.cannon:
http://hg.python.org/devguide/rev/a34e4a6b89dc
changeset: 489:a34e4a6b89dc
user:Brett Cannon br...@python.org
date:Tue Jan 24 12:58:01 2012 -0500
summary:
Use -j0 to maximimze parallel execution.
files:
runtests.rst | 2 +-
Am 28.01.2012 02:19, schrieb Benjamin Peterson:
Hello everyone,
In effort to get a fix out before Perl 6 goes mainstream, Barry and I
have decided to pronounce on what we want for our stable releases.
What we have decided is that
1. Simple hash randomization is the way to go. We think this
Am 29.01.2012 08:42, schrieb Ethan Furman:
Benjamin Peterson wrote:
2012/1/26 Ethan Furman et...@stoneleaf.us:
PEP: XXX
Congratulations, you are now PEP 409.
Thanks, Benjamin!
So, how do I make changes to it?
Please send PEP updates to the PEP editors at p...@python.org.
Georg
Am 31.01.2012 00:50, schrieb Matt Joiner:
Sounds good, but I also prefer Alexander's method. The type information is
already encoded in the class object. This way you don't need to maintain a
mapping of strings to classes, and other functions/third party can join in the
fun without needing
Am 30.01.2012 20:06, schrieb stefan brunthaler:
Do you have a public repository for the code, so we can take a look?
I have created a patch (as Benjamin wanted) and put all of the
resources (i.e., benchmark results and the patch itself) on my home
page:
Am 31.01.2012 13:08, schrieb Victor Stinner:
This way you don't need to maintain a
mapping of strings to classes, and other functions/third party can join in
the fun without needing access to the latest canonical mapping. Lastly there
will be no confusion or contention for duplicate keys.
Am 31.01.2012 16:46, schrieb stefan brunthaler:
If I read the patch correctly, most of it is auto-generated (and there
is probably a few spurious changes that blow it up, such as the
python-gdb.py file).
Hm, honestly I don't know where the python-gdb.py file comes from, I
thought it came
401 - 500 of 1517 matches
Mail list logo
