Martin Blais schrieb:
> On 5/22/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>>
>> So in Armin's example, I found the reST version *much* easier to read.
>> Whether that difference in perception is due simply to my relative lack
>> of experience in using LaTeX, or to something else, I have no idea.
Raymond Hettinger schrieb:
>> - If you make a mistake in LaTeX, you will get a cryptic error which
>> is usually a little difficult to figure out (if you're not used to
>> it). You can an error though.
>
> FWIW, the pure Python program in Tools/scripts/texchecker.py does a
> pretty good job of
Steve Holden schrieb:
> Titus Brown wrote:
>> On Tue, May 22, 2007 at 11:45:04AM -0500, [EMAIL PROTECTED] wrote:
>> ->
>> -> >> You at least take away a common excuse for lack of contributions.
>> -> >> True whiners will just come up with new ones (e.g., "the
>> -> >> documentation isn
BJörn Lindqvist schrieb:
>> > IMO that pair of examples shows clearly that, in this application,
>> > reST is not an improvement over LaTeX in terms of readability/
>> > writability of source. It's probably not worse, although I can't help
>> > muttering "EIBTI". In particular I find the "``'...'
Armin Ronacher schrieb:
> Hoi,
>
> Additionally to the offline docs that Georg published some days ago there is
> also a web version which currently looks and works pretty much like the
> offline
> version. There are however some differences that are worth knowing:
>
> - Cleaner URLs. You can ac
Georg Brandl schrieb:
> Armin Ronacher schrieb:
>> Hoi,
>>
>> Additionally to the offline docs that Georg published some days ago there is
>> also a web version which currently looks and works pretty much like the
>> offline
>> version. There are however
Nick Craig-Wood schrieb:
>> > It is missing conversion of ``comment'' at the moment as I'm sure you
>> > know...
>>
>> Sorry, what did you mean?
>
> ``comment'' produces smart quotes in latex if I remember correctly.
> You probably want to convert it somehow because it looks a bit odd on
> the
Bug #1722485 reports that Py 2.5+ doesn't ignore docstrings anymore if
used with -OO.
Attached patch should fix this.
Georg
Index: Python/compile.c
===
--- Python/compile.c (Revision 55526)
+++ Python/compile.c (Arbeitskopie)
@@ -111
Nick Craig-Wood schrieb:
>> > It is missing conversion of ``comment'' at the moment as I'm sure you
>> > know...
>>
>> Sorry, what did you mean?
>
> ``comment'' produces smart quotes in latex if I remember correctly.
> You probably want to convert it somehow because it looks a bit odd on
> the
Talin schrieb:
> Martin Blais wrote:
>> On 5/22/07, Martin Blais <[EMAIL PROTECTED]> wrote:
>>> ReST works well only when there is little markup. Writing code
>>> documentation generally requires a lot of markup, you want to make
>>> variables, classes, functions, parameters, constants, etc.. (A
Ron Adam schrieb:
> Nick Craig-Wood wrote:
> > On Wed, May 23, 2007 at 12:46:50PM -0500, Ron Adam wrote:
> >> Nick Craig-Wood wrote:
> >>> So I'll be able to read the main docs for a module in a terminal
> >>> without reaching for the web browser (or info)? That would be great!
> >>>
> >>> H
Martin v. Löwis schrieb:
> Michael Foord schrieb:
>> This subject is generating a lot of discussion and [almost entirely]
>> positive feedback. It would be a great shame to run out of steam.
>>
>> Does it need a PEP to see a chance of it getting accepted as the formal
>> documentation system? (o
Neal Norwitz schrieb:
> On 5/25/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> In my bcannon-objcap branch I am trying to check in a change that involves a
>> soft symlink from Lib/controlled_importlib.py to
>> ../importlib/controlled_importlib.py through ``ln -s
>> ../controlled_importlib.py contr
Hi,
We managed to get an up to date version of the web version of the docs running
on the server. The address is still the same (http://pydoc.gbrandl.de:3000) and
it's also still running on top of wsgiref.
Changes so far:
* comments: each page that is generated from an rst file can have some
Neal Norwitz schrieb:
> On 5/26/07, Peter Åstrand <[EMAIL PROTECTED]> wrote:
>>
>> I'm unable to commit tonight:
>>
>> SendingDoc/lib/libsubprocess.tex
>> SendingLib/subprocess.py
>> SendingLib/test/test_subprocess.py
>> Transmitting file data ...svn: Commit failed (details
Martin v. Löwis schrieb:
>> Odd... the call worked here (SVN 1.4.3). Which version is the server using?
>
> 1.1. Subversion did a grand renaming at some point. I fixed most of the
> functions when deploying the script, but apparently missed some.
Okay. Is an upgrade planned? I've heard that sever
Scott Dial schrieb:
> Martin v. Löwis wrote:
>> Brett Cannon schrieb:
>>> Unfortunately the pre-commit hook
>>> does not specify what line a change was made on so I have no clue where
>>> it is failing (maybe this should be added?).
>>
>> It creates a reindent.Reindenter on the new contents, then
Martin v. Löwis schrieb:
>> As I said before, you don't really need that when you can (and should!) just
>> run
>> reindent.py over the source file yourself, not care about any diffs and just
>> resubmit.
>
> Right. So I withdraw my offer to do anything about the hook.
I think printing something
Raghuram Devarakonda schrieb:
> There is an entry in "Core and builtins" section of Misc/NEWS:
>
> "Bug #1722484: remove docstrings again when running with -OO.".
>
> The actual bug is 1722485. Incidentally, 1722484 appears to be spam.
Fixed, thanks for spotting (you really read the commit logs
Eyal Lotem schrieb:
> Hi. It seems that cProfile does not support throwing exceptions into
> generators properly, when an external timer routine is used.
>
> The problem is that _lsprof.c: ptrace_enter_call assumes that there
> are no exceptions set when it is called, which is not true when the
>
A.M. Kuchling schrieb:
> What was the outcome of the discussion of Georg Brandl's reworked
> documentation ("The docs, reloaded")? Was any decision made on
> whether to go with reST, or on what changes need to made before that's
> possible? Did Fred Drake say what he thought?
For my part, I'm st
Guido van Rossum schrieb:
> I've written up a comprehensive status report on Python 3000. Please read:
>
> http://www.artima.com/weblogs/viewpost.jsp?thread=208549
Thank you! Now I have something to show to interested people except "read
the PEPs".
A minuscule nit: the rot13 codec has no library
Hi,
we got another feature request for multi-line comments.
While it is nice to comment out multiple lines at once, every editor
that deserves that name can add a '#' to multiple lines.
And there's always "if 0" and triple-quoted strings...
Georg
___
Walter Dörwald schrieb:
If a PEP is called for, I'd be happy to at least co-author it.
>>> Codecs are a major exception to Guido's law: Never have a parameter
>>> whose value switches between completely unrelated algorithms.
>>
>> I don't think that applies here. This is more like __import__
Guido van Rossum schrieb:
> On 6/19/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
>> we got another feature request for multi-line comments.
>>
>> While it is nice to comment out multiple lines at once, every editor
>> that deserves that name can add a
Guido van Rossum schrieb:
> Those are valid concerns. I'm cross-posting this to the python-3000
> list in the hope that the PEP's author and defendents can respond. I'm
> sure we can work something out.
Another question w.r.t. new string formatting:
Assuming the %-operator for strings goes away a
Guido van Rossum schrieb:
> How important is it to have the default in this API? __getitem__()
> doesn't have a default; instead, there's a separate API get() that
> provides a default (and I find defaulting to None more manageable than
> the "_default = object()" pattern).
getattr() has a default
Dear fellow Pythonistas,
as you may have heard, Python is going to get a new documentation system
soon [1]. As part of that effort, and in order to maintain the excellent
quality of the docs, we are looking for members of the maintainers team.
This is your chance to get involved with Python devel
Talin schrieb:
> In PEP 9 there's a requirement that PEPs must follow the "emacs
> convention" of 2 spaces after a period. (I didn't know this was an emacs
> convention, I thought it was a convention of people who used typewriters.)
It's an Emacs convention in the sense that its auto-filling fun
Raymond Hettinger schrieb:
> The docs do make a distinction and generally follow the definitions given in
> the glossary for the tuturial.
>
> In the case of iter(collection), I prefer the current wording because the
> target object need not support __iter__, it is sufficient to supply a
> sequent
[EMAIL PROTECTED] schrieb:
> Pete> That points towards a way forward. Why do programming languages
> Pete> continue to assume use of a monospaced font? It was natural when
> Pete> we used punch cards and line printers, but now? Python relies on
> Pete> the indentation but could b
Lisandro Dalcin schrieb:
> Porting to Py3K, I modified a function like the followin, using a
> trick for it working in Py2.x .
>
> def __iter__(self):
> if self == _mpi.INFO_NULL:
> return
> try:range = xrange
> except: pass
> nkeys = _mpi.info_g
Greg Ewing schrieb:
> Georg Brandl wrote:
>> I couldn't live without monospaced fonts for
>> source code. Apart from being easier to read, it is essential for sketches
>> or things that must be aligned, such as the class schema in SocketServer.py.
>
> This just
Guido van Rossum schrieb:
> NonImplemented isn't treated as special when returned by __cmp__();
> __cmp__ is not considered a binary operator like __add__. (__lt__ and
> friends *do* get treated as such -- but instead of __rlt__ we use
> __gt__, etc.)
But if it's not treated as special, why doesn'
Facundo Batista schrieb:
> 2007/8/2, Guido van Rossum <[EMAIL PROTECTED]>:
>
>> NonImplemented isn't treated as special when returned by __cmp__();
>> __cmp__ is not considered a binary operator like __add__. (__lt__ and
>> friends *do* get treated as such -- but instead of __rlt__ we use
>> __gt_
Terry Reedy schrieb:
> "Facundo Batista" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> | >>> class C(object):
> | ... def __cmp__(self, other):
> | ... return NotImplemented
> | ...
>
> Given that you 'should' return an int, doing elsewise has undefined
> results.
Sure, you could use ``iter(())`` or ``iter([])``, but for consistency's sake
wouldn't it make sense for ``iter()`` to return an empty iterator, as ``str()``
returns an empty string etc.?
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number
See bugs #1548891 and #1730114.
In the former, it was reported that cStringIO works differently from StringIO
when handling unicode strings; it used GetReadBuffer which returned the raw
internal UCS-2 or UCS-4 encoded string.
I changed it to use GetCharBuffer, which converts to a string using the
Guido van Rossum schrieb:
> Methinks that this was a fundamental limitation of cStringIO, not a
> bug. Certainly not something to be "fixed" in a bugfix release.
I'm sorry.
Martin v. Löwis schrieb:
>> See bugs #1548891 and #1730114.
>>
>> In the former, it was reported that cStringIO works diff
Nick Maclaren schrieb:
> Further to the above, I found the Unicode sources, have rebuilt
> the files, but it involved some fairly serious hacking to the
> building mechanism and I have had to disable the Unicode 3.2
> support. And, of course, that means that 4 of the tests fail.
>
> This area nee
Can somebody please review this patch:
https://sourceforge.net/support/tracker.php?aid=1692335
It aims to fix the pickling of exceptions whose __init__ methods don't call
Exception.__init__ at all, or with a different number of arguments.
This should be fixed before 2.5.2.
Georg
--
Thus spake
Paul Moore schrieb:
> Specifically, I'm looking to replicate this behaviour:
>
>>xxd crlf
> 000: 610d 0a62 0d0a a..b..
>
>>xxd lf
> 000: 610a 620aa.b.
>
>>python
> Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 b
Neal Norwitz schrieb:
> On 8/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> Georg Brandl schrieb:
>> >
>> > Neal will change his build scripts, so that the 2.6 and 3.0 devel
>> > documentation pages at docs.python.org will be built from these new
>
O.R.Senthil Kumaran schrieb:
> Hello All,
>
> I am drafting a PEP proposing a module 'urilib', which will be the unified
> module of urlparse, urllib and urllib2.
>
> a) _all_ functions will include from urlparse,urllib and urllib2. b)
> overlapping functionality between urllib and urllib2 to be
Amaury Forgeot d'Arc schrieb:
> Hello,
>
> Martin v. Löwis wrote:
>> I think the obvious thing you missed is that the problem got fixed
>> already. Whether the documentation system should be more defensive and
>> work with 2.5.0 also is a different question.
>
> You are right. python 2.5.1 correc
Paul Moore schrieb:
> On 21/08/07, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>>
>>
>> On 8/14/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> > Now that the converted documentation is fairly bug-free, I want to
>> > make the switch.
>>
&g
Thomas Wouters schrieb:
>
>
> On 8/14/07, *Georg Brandl* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
> Now that the converted documentation is fairly bug-free, I want to
> make the switch.
>
>
> One thing I miss (and I have
Benji York schrieb:
> Georg Brandl wrote:
>> I put the CHM at <http://www.python.org/~gbrandl/pydoc.chm>, if you want
>> to have a look.
>
> Generally looks good. I did get this error when opening the CHM:
>
> """
> A Runtime Error has occur
Paul Moore schrieb:
> On 21/08/07, Benji York <[EMAIL PROTECTED]> wrote:
>> Georg Brandl wrote:
>> > I put the CHM at <http://www.python.org/~gbrandl/pydoc.chm>, if you want
>> > to have a look.
>>
>> Generally looks good. I did get this error
Neal Becker schrieb:
> I'm interested in trying out new style (python 2.6) documentation. I see
> we're using docutils + sphinx?
>
> I did: svn co http://svn.python.org/projects/doctools/trunk/
>
> How can I install this to try it with python-2.5?
What do you want to try with Python 2.5?
If yo
Neal Becker schrieb:
> Georg Brandl wrote:
>
>> Neal Becker schrieb:
>>> I'm interested in trying out new style (python 2.6) documentation. I see
>>> we're using docutils + sphinx?
>>>
>>> I did: svn co http://svn.python.org/projects
Martin v. Löwis schrieb:
> Together with David Bolen, I set up a series of buildbot
> slaves that create an MSI installer from the 2.5, 2.6,
> and 3.0 branches every day. The result files are available
> from
>
> http://www.python.org/dev/daily-msi/
>
> The buildbot pages themselves are at
>
> h
David Bolen schrieb:
> Georg Brandl <[EMAIL PROTECTED]> writes:
>
>> I hope this isn't due to the files that Sphinx creates.
>> I had a nasty crash with HTML Help Workshop when I generated
>> an "invalid" index file -- but this was reproducible of c
Martin v. Löwis schrieb:
>> In the 2.x docs, all versionadded strings should stay. But IMO in the
>> 3.0 docs we should get rid of them all. If you want compatibility
>> information, look at the 2.6 docs (those should also mention things
>> that are changing in 3.0).
>
> I agree. People who target
[EMAIL PROTECTED] schrieb:
> I'd like to help out cleaning up the Python3.0 documentation. There are a
> lot of little leftovers from 2.x that are no longer true. (mentions of
> long, callable() etc.)
I've applied the first four patches, thank you!
Georg
--
Thus spake the Lord: Thou shalt ind
Eli Courtwright schrieb:
> Greetings,
>
> I've found what might be a bug in Python's % string formatting
> operator. Consider the following code:
>
> "%%(%s)=%%s" % "hello"
>
> On "Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) [GCC 3.4.4 (cygming
> special, gdc 0.12, using dmd 0.125)] on cyg
Hi,
as you may have seen in the checkins, I just created a new chapter
in the docs called "Using Python."
We, the doc team, would like that section to contain, roughly,
information how to install Python on different platforms, how to
configure it, how to invoke it, what extra things and quirks yo
Thomas Heller schrieb:
> I've just received a private email from Christian Jacobsen (we were discussing
> some ctypes bugs/deficiencies that do not matter in this context). He wrote:
>
>> [...] The bug
>> reporting procedures for documentation is a big inconsistent:
>> http://wiki.python.org/moin
Guido van Rossum schrieb:
> Cool! Is it just a matter of checking this in and it will work on the site?
No. The current newstyle docs (2.6, 3.0) are static HTML pages.
However, Sphinx can also generate slightly different output which
is then used by a web app that has all the dynamic features for
Guido van Rossum schrieb:
> I'd like to make this a standard built-in, in the hope the debate on
> how to declare settable properties.
+1. I'm waiting for the obligatory cry for @propdel though :)
> I'd also like to change property so that the doc string defaults to
> the doc string of the gette
Christian Heimes schrieb:
> Hello!
>
> I'm having a bit of a trouble getting the deprecation warning for
> backquotes `repr` right. Neither the ast_for_* functions in Python/ast.c
> nor the node structures have access to the filename.
On a related note, every time you start a Python interpreter w
Andreas Raab schrieb:
> Hi -
>
> I'm having a few problems with our (embedded) Python interpreter trying
> to write .pyc files in the installation of our product (which actually
> sometimes works and sometimes doesn't depending on OS and paranoia level
> involved). This can give raise to a few
Facundo Batista schrieb:
> 2007/11/23, Christian Heimes <[EMAIL PROTECTED]>:
>
>> Well, I'm exaggerating a bit but you probably get my point. The core
>> developers can't keep up with new bugs and check old bugs at the same
>> time. The resources are already stretched thin. But Brett gave me an
>
Facundo Batista schrieb:
>> won't need developer access to the svn. Instead their task is cleaning
>> up the tracker, categorizing bugs and checking patches. The tracker sure
>> contains a lot of outdated junk and already fixed bugs.
>
> One way to do this is to create a monthly (or each two mont
Christian Heimes schrieb:
> Dear fellow Python developers!
>
> The Python bug tracker contains more than 1,300 bugs and it's growing.
Not speaking of the 432 bugs that weren't migrated from SourceForge
(though I don't know how many of them were open).
> And growing ... and growing. I'm picking a
Titus Brown schrieb:
> Dear Python-Dev-ers,
>
> about half of the tasks for the GHOP contest (described below) are
> currently on the stdlib, Python core, or Py3K:
>
>
> http://code.google.com/p/google-highly-open-participation-psf/issues/list?q=label:stdlib
>
>
> http://code.googl
Christian Heimes schrieb:
> I'm sending this mail to Python-dev in the hope to reach more developers.
>
> GvR likes to rename the __builtin__ to reduce confusing between
> __builtin__ and __builtins__. He wanted to start a poll on the new name
> but apparently he forgot.
>
>>From http://bugs.pyth
Paul Moore schrieb:
> On 28/11/2007, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> Christian Heimes schrieb:
>> > What name do you prefer? I'm +1 with Raymond on __root__ but I'm still
>> > open for better suggestions.
>>
>> FWIW, +1 for __r
Steve Holden schrieb:
>> What name do you prefer? I'm +1 with Raymond on __root__ but I'm still
>> open for better suggestions.
>>
> The namespace should really be called __global__. I doubt this will fly,
> because it's too radical, and unfortunately would undermine the "global"
> keyword, use
Christian Heimes schrieb:
> Adam Olsen wrote:
>> -1 on __python__. It seems to be an abbreviation of "python
>> interpreter core" or the like, but on its own it implies nothing about
>> what it means.
>>
>> Contrast that with __root__ where we all know what a root is, even
>> though it doesn't im
Guido van Rossum schrieb:
>> > On Nov 30, 2007, at 6:05 PM, Guido van Rossum wrote:
>> >> It's almost as if nobody has seen my proposal to leave __builtins__
>> >> alone and rename the __builtin__ module instead.
>
>> Fred Drake wrote:
>> > +1 for a module named "builtin", or something similarly o
Antoine Pitrou schrieb:
> Hi,
>
> (I was asked to forward this from the bug tracker)
>
>> We have also run into problems where a task tries to "return" (yield
>> Return())
>> from within a try: except Exception: block. Since returning from a
>> coroutine is
>> roughly equivalent to "raise Gene
Guido van Rossum schrieb:
> On Dec 2, 2007 7:40 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>> Just for the record, I also like the idea of __builtins__ being a magic
>> alias for the boringly-but-practically named builtins module.
>
> [Imagine me jumping up and down and screaming at the top of my
Antoine Pitrou schrieb:
> Le dimanche 02 décembre 2007 à 12:08 -0800, Neal Norwitz a écrit :
>> Note that StandardError was removed from py3k.
>
> Out of curiosity, what is the reason for this? Another exception tree
> rearrangement?
I think it was found not to serve a real purpose.
Georg
--
T
Neil Toronto schrieb:
> So Jim and PJE finally convinced me to do it the right way. :) Thanks
> guys - it turned out very nice.
How does this relate to Armin Rigo's method cache patch?
(http://bugs.python.org/issue1685986)
Georg
___
Python-Dev mailin
Steve Holden schrieb:
> Christian Heimes wrote:
>> Good afternoon everybody!
>>
>> The new C API documentation contains some large files:
>>
>> 105K abstract.html
>> 300K concrete.html
>> 183K newtypes.html
>>
>> The concrete.html takes noticeable time to render on my computer (P4 2.4
>> with 1G
Giampaolo Rodola' schrieb:
> O.T. - I noticed that the PEP-3 still refers to the old sourceforge
> bug tracker. Shouldn't it be rewritten?
Yes, thanks! I did a minimal change, but still someone could elaborate
it, describing current practices.
Georg
--
Thus spake the Lord: Thou shalt indent wit
Hi,
there wasn't much response to the bug day proposal, but I still think it's
a good idea. I'd propose a date in January, when Christmas etc. is over.
It would also be nice if someone did the organizing who hasn't got a
daily batch of GHOP tasks to review and commit :)
Georg
--
Thus spake the
A.M. Kuchling schrieb:
> On Fri, Dec 07, 2007 at 10:04:38PM +0100, Georg Brandl wrote:
>> there wasn't much response to the bug day proposal, but I still think it's
>> a good idea. I'd propose a date in January, when Christmas etc. is over.
>> It would also b
Hi,
just wanted to let you know that I've added a LaTeX builder to the doctools,
so that one can produce LaTeX source from the docs again. It uses the old
python.sty package, for which I feel grateful.
You should be able to build the PDFs with a "make latex" in Doc, and a
"make all-pdf" in Doc/bu
Christian Heimes schrieb:
> Mike Klaas wrote:
>> Question: should patches include edits to whatsnew.rst, or is the
>> committer responsible for adding a note?
>
> A patch should contain edits for Misc/NEWS.
And documentation changes should include proper "versionchanged" or
"versionadded" tags
Jay schrieb:
Only addressing the easier points here:
> #--
> # flaw #2
> #
> # In functions, reads are scoped. Writes are not.
> #
>
> A = "1"
>
> def F1():
> A = "2" # not an error
>
> def F2():
> #B = A # error
> A = "3"
>
Python accepts 0x as an integer literal. Is this intended (the docs
say otherwise, but int() and tokenize.py concur)?
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 be
A.M. Kuchling schrieb:
> Today's bug day was a great success. Experienced people like Georg,
> Facundo, and Gregory P. Smith participated, and we also had people who
> submitted their first patches, some of which got applied today, too.
> Hopefully we'll see those people again.
>
> As of this w
Martin v. Löwis schrieb:
> After some months of tracker operation, I'd like to discuss one aspect
> of the tracker schema: priorities.
>
> Each issue has a severity and a priority. The severity is assigned by
> the submitter, defaults to normal, and indicates how serious the issue
> impacts him an
A.M. Kuchling schrieb:
> Today's bug day was a great success. Experienced people like Georg,
> Facundo, and Gregory P. Smith participated, and we also had people who
> submitted their first patches, some of which got applied today, too.
> Hopefully we'll see those people again.
>
> As of this w
Tristan Seligmann schrieb:
> * Oleg Broytmann <[EMAIL PROTECTED]> [2008-01-20 20:12:38 +0300]:
>
>> On Sun, Jan 20, 2008 at 06:00:31PM +0100, Christian Heimes wrote:
>> > #!/usr/bin/env python -E -s
>>
>>On most Unicies #! magic may have only one parameter after the program;
>> the program he
Paul Moore schrieb:
> On 24/01/2008, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
>> int has to be a builtin because it's a fundamental type. trunc()
>> followed round() into the builtins. I have no opinion on whether ceil
>> and floor should move there; it probably depends on how often they're
>> us
Brett Cannon schrieb:
> I noticed on the download page that http://www.python.org/emacs is
> listed as the place to get your modes for Python development (which
> seemed to lack any mention of Vim and the support in svn; a slight
> bias =). Is this true for core development as well?
>
> Basically
Eric Smith schrieb:
> While implementing "".format(), I need to call the builtin format()
> function, which I've already implemented (in
> bltinmodule.c:builtin_format()). In the py3k branch, I just hardcoded
> the same functionality into "".format(), which seems like the wrong
> thing to do, giv
Christian Heimes schrieb:
> Good evening everybody!
>
> I like to run the 2to3 tool with raise and except fixers over the 2.6
> sources. The raise fixer changes "raise Exception, msg" to "raise
> Exception(msg)" and the except fixer replaces "except Exception, err" by
> "except Exception as err".
Steve Holden schrieb:
> Jeroen Ruigrok van der Werven wrote:
>> -On [20080218 21:41], Brett Cannon ([EMAIL PROTECTED]) wrote:
>>> My issue with keeping the RFEs in the tracker as they are is that it
>>> artificially inflates the open issue count. Python does not have over
>>> 1,700 open bugs.
>>
>
Nick Coghlan schrieb:
> Brett Cannon wrote:
>> My issue with keeping the RFEs in the tracker as they are is that it
>> artificially inflates the open issue count. Python does not have over
>> 1,700 open bugs.
>
> That's a problem with our status reporting, not with the fact that there
> are RFE's
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
Martin v. Löwis schrieb:
>> 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?)
>
> I would find it
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 reache
[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?
N
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
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
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, w
901 - 1000 of 1594 matches
Mail list logo
