Hi!
I think you were the omitting the more interesting closure examples
(namely with free variables inside the closure's source):
def foo(): pass
def bar(x):
def fiep(): return x()
return fiep
what's bar(foo).__source__?
Generally, I'm opposed to the feature -- I don't think it provides a
r
I have a PC with an AMD cpu and Mandrake 10.1. While installing Python
2.4 "make test" failed in "test_shutils.py". Here is the output of
"./python ./Lib/test/test_shutil.py":
test_dont_copy_file_onto_link_to_itself (__main__.TestShutil) ... ok
test_dont_move_dir_in_itself (__main__.TestShutil)
Stelios Xanthakis wrote:
Now that 2.4 is out and everything maybe it's
about time to start discussing the "use the
__source__ Luke" feature which IMO will really
boost python into a new domain of exciting
possibilities.
I'm opposed to this idea. It creates overhead in
the size of .pyc files, for no
On Fri, 3 Dec 2004, holger krekel wrote:
...
there is another possibility for storing "source" or any other such meta
information with code/module objects: make __file__ and co_filename
instances of a subclass of 'str' providing an extra attribute.
For a simple example, they could have a 'source'
"A.M. Kuchling" <[EMAIL PROTECTED]> writes:
> Perhaps the summaries should include an "unassigned bugs" list to nag
> us to look at bugs and assign them to the right person.
The bug report is derived from the bug and patch email lists, so that
information isn't available without scraping it off
Fredrik Lundh pythonware.com> writes:
> Bjorn Tillenius wrote:
> > There are some issues regarding the use of unicode in doctests. Consider
> > the following three tests.
> >
> >>>> foo = u'fÃÃ'
> >>>> foo
> >u'f\xf6\xf6'
> >
> >>>> foo
> >u'f\u00f6\u00f6'
> >
> >>>> foo
>
M.-A. Lemburg wrote:
Here's an update of the list I currently have:
* MS VS6 SP5 (International version, optimizing VC6 compiler with SP5):
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
* MS VC6 (German versi
Here's an update of the list I currently have:
* MS VS6 SP5 (International version, optimizing VC6 compiler with SP5):
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
* MS VC6 (German version; optimizing VC6 co
I would like to remove the support for using libc wctype functions
(e.g. towupper(), towlower(), etc.) from the code base.
The reason is that compiling Python using this switch not only
breaks the test suite, it also causes the functions .lower() and
.upper() to become locale aware and creates wron
Bjorn Tillenius wrote:
> There are some issues regarding the use of unicode in doctests. Consider
> the following three tests.
>
>>>> foo = u'föö'
>>>> foo
>u'f\xf6\xf6'
>
>>>> foo
>u'f\u00f6\u00f6'
>
>>>> foo
>u'föö'
>
> To me, those are identical.
really? if a functi
Hi Stelios,
[Stelios Xanthakis Fri, Dec 03, 2004 at 11:54:25AM +0200]
> Abstract
>
> This PEP suggests the implementation of __source__ attribute for
> functions and classes. The attribute is a read-only string which
> is generated by the parser and is a copy of the original source
Hi all.
Now that 2.4 is out and everything maybe it's
about time to start discussing the "use the
__source__ Luke" feature which IMO will really
boost python into a new domain of exciting
possibilities.
I've prepared a pre-PEP which is not very good
but it is a base.
In short, the feature is good a
12 matches
Mail list logo
