In article <4c62c01d.6000...@netwok.org>,
Ãric Araujo wrote:
> Hello list
>
> Tarek opened a distutils bugs in http://bugs.python.org/issue7175 that
> evolved into a discussion about the proper location to use for config files.
>
> Distutils uses [.]pydistutils.cfg and .pypirc, and now unitte
On Wed, Aug 11, 2010 at 10:58 PM, Éric Araujo wrote:
> Considering the FHS or the XDG Base
> Directory specifications, there is a precedent in distinguishing user
> config (edited by the user through a text editor or settings graphical
> window), program data (state) and cache (files for speedups
> PEP 370 already specifies a directory for Python config files:
>
>> user data directory
>>
>> Usually the parent directory of the user site directory.
>> It's meant for Python version specific data like config
>> files, docs, images and translations.
Thanks for pointing that. Howeve
> I'd like to see a more complete proposal, including:
Fair enough.
tl;dr: Locating config files is hard.
I have looked at http://github.com/ActiveState/appdirs (MIT) for
OS-specific bits of knowledge. (Note that the directories it uses for
free OSes are not compliant with the freedesktop.org Bas
On 8/11/2010 5:37 PM, Terry Reedy wrote:
> On 8/11/2010 3:16 PM, Raymond Hettinger wrote:
>
>> The ability to introspect is basic to Python's design.
>> Objects know their class, functions know their code objects,
>> bound methods know both their underlying function,
>> classes know their own clas
On Aug 11, 2010, at 3:28 PM, Benjamin Peterson wrote:
> 2010/8/11 Raymond Hettinger :
>>
>> On Aug 11, 2010, at 2:37 PM, Terry Reedy wrote:
>>
>>> On 8/11/2010 3:16 PM, Raymond Hettinger wrote:
>>>
The ability to introspect is basic to Python's design.
Objects know their class, funct
On Wed, 2010-08-11 at 13:10 +1000, Nick Coghlan wrote:
> On Wed, Aug 11, 2010 at 12:39 PM, Benjamin Peterson
> wrote:
> > which would require ignoring the absence of __annotations__.
>
> It turns out the patch that added __annotations__ support also made a
> change to make all of the copied attr
Hello,
Fred Drake fdrake at acm.org wrote:
> +0.5
>
> I'd like to see a more complete proposal, including:
>
> - what to do with Windows, Mac OS X
PEP 370 already specifies a directory for Python config files:
> user data directory
>
> Usually the parent directory of the user site directory.
2010/8/11 Raymond Hettinger :
>
> On Aug 11, 2010, at 2:37 PM, Terry Reedy wrote:
>
>> On 8/11/2010 3:16 PM, Raymond Hettinger wrote:
>>
>>> The ability to introspect is basic to Python's design.
>>> Objects know their class, functions know their code objects,
>>> bound methods know both their unde
On Aug 11, 2010, at 2:37 PM, Terry Reedy wrote:
> On 8/11/2010 3:16 PM, Raymond Hettinger wrote:
>
>> The ability to introspect is basic to Python's design.
>> Objects know their class, functions know their code objects,
>> bound methods know both their underlying function,
>> classes know their
On Wed, Aug 11, 2010 at 11:21 PM, Nick Coghlan wrote:
> However, as I noted before, these kinds of scenario are the reason we
> decided that building this feature directly into the decorator
> machinery wasn't a good idea.
I agree. I was just replying to Steven's response to my post. :)
Schiavo
On 8/11/2010 3:16 PM, Raymond Hettinger wrote:
The ability to introspect is basic to Python's design.
Objects know their class, functions know their code objects,
bound methods know both their underlying function,
classes know their own class dictionary, etc.
Should iterators know their iterab
On Thu, Aug 12, 2010 at 12:12 AM, Simon Cross
wrote:
> Yes. But it's more common for the original function to have be
> modified in some way. e.g.:
>
> def autodoc(f):
> f.__doc__ += document_args(f)
> return f
>
> @autodoc
> def f(x, y):
> """Add two numbers"""
> return x + y
>
> An
On Thu, Aug 12, 2010 at 1:45 AM, Ronald Oussoren wrote:
>
> On 11 Aug, 2010, at 16:21, Tim Golden wrote:
>
>> Thanks to whoever's been working on the new Summary lists on the Issue
>> Tracker.
>> The "Followed by you" / "Created by you" / "Assigned to you" are just what
>> the doctor ordered.
>
>
On Thu, Aug 12, 2010 at 1:55 AM, Fred Drake wrote:
> On Wed, Aug 11, 2010 at 11:28 AM, Mark Dickinson wrote:
>> Well, perhaps I'm the only person bothered by this (and when I say
>> 'bothered', it's not exactly keeping me up at nights).
>
> I'm not going to lose sleep over it either, but the logo
On Aug 11, 2010, at 6:00 AM, Steven D'Aprano wrote:
> @wraps(f)
> def func(*args):
>do_something()
>return f(*args)
>
> then func.__wrapped__ gives f. If f itself wraps (say) g, and g wraps h,
> then you have:
>
> func.__wrapped__ => f
> func.__wrapped__.__wrapped__ => g
> func.__wrapp
On Wed, Aug 11, 2010 at 11:28 AM, Mark Dickinson wrote:
> Well, perhaps I'm the only person bothered by this (and when I say
> 'bothered', it's not exactly keeping me up at nights).
I'm not going to lose sleep over it either, but the logo-link is
generally considered very non-discoverable. Keepi
On Wed, Aug 11, 2010 at 11:22 AM, Éric Araujo wrote:
> Tarek, Antoine, RDM, MAL were +1 on using ~/.python (whether to use
> .pythonx.y or .python/x.y is a subissue to discuss after general agreement).
+0.5
I'd like to see a more complete proposal, including:
- what to do with Windows, Mac OS X
On Wed, Aug 11, 2010 at 03:21:15PM +0200, Sturla Molden wrote:
>
> "David Cournapeau":
> > Autotools only help for posix-like platforms. They are certainly a big
> > hindrance on windows platform in general,
>
> That is why mingw has MSYS.
>
> mingw is not just a gcc port, but also a miniature g
On 11/08/2010 16:45, Ronald Oussoren wrote:
On 11 Aug, 2010, at 16:21, Tim Golden wrote:
Thanks to whoever's been working on the new Summary lists on the Issue Tracker.
The "Followed by you" / "Created by you" / "Assigned to you" are just what
the doctor ordered.
I'm not quite happy about th
On 11 Aug, 2010, at 16:21, Tim Golden wrote:
> Thanks to whoever's been working on the new Summary lists on the Issue
> Tracker.
> The "Followed by you" / "Created by you" / "Assigned to you" are just what
> the doctor ordered.
I'm not quite happy about them because these reports include closed
On 11/08/2010 16:22, Éric Araujo wrote:
Hello list
Tarek opened a distutils bugs in http://bugs.python.org/issue7175 that
evolved into a discussion about the proper location to use for config files.
Distutils uses [.]pydistutils.cfg and .pypirc, and now unittest2 has a
config file too.
ID
On Wed, Aug 11, 2010 at 4:09 PM, Ezio Melotti wrote:
> On 11/08/2010 17.59, Mark Dickinson wrote:
>> One niggle: we seem to have lost the simple 'Open Issues' search
>> under 'Summaries' on the left-hand side of the page.
>
> I was expecting someone to complain about it.
Glad to oblige. :)
> T
Hello list
Tarek opened a distutils bugs in http://bugs.python.org/issue7175 that
evolved into a discussion about the proper location to use for config files.
Distutils uses [.]pydistutils.cfg and .pypirc, and now unittest2 has a
config file too.
It would be nice to define one standard location
On 11/08/2010 17.59, Mark Dickinson wrote:
On Wed, Aug 11, 2010 at 3:21 PM, Tim Golden wrote:
Thanks to whoever's been working on the new Summary lists on the Issue
Tracker.
Ezio Melotti, I assume.
Yes :)
(see http://psf.upfronthosting.co.za/roundup/meta/issue329)
The "Followed by you" /
On Wed, Aug 11, 2010 at 3:21 PM, Tim Golden wrote:
> Thanks to whoever's been working on the new Summary lists on the Issue
> Tracker.
Ezio Melotti, I assume.
> The "Followed by you" / "Created by you" / "Assigned to you" are just what
> the doctor ordered.
Agreed. Now I can get rid of my own
I think this is a good idea, because sometimes getting the innermost wrapped
function from a wrapper function is very useful. For example, when I use
inspect.getsource(), in most case, I want to get the source code of the
wrapped function, not the wrapper, because the wrapped function usually
conta
Thanks to whoever's been working on the new Summary lists on the Issue
Tracker.
The "Followed by you" / "Created by you" / "Assigned to you" are just what
the doctor ordered.
TJG
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/
On Wed, Aug 11, 2010 at 3:00 PM, Steven D'Aprano wrote:
>> * The decorator returns the original function (I suppose a reference
>> to itself is okay?)
>
> There's no reason why a function can't have an attribute that refers to
> the function itself. It works fine:
Yes. But it's more common for th
On Tue, 10 Aug 2010 15:25:52 -0400
Terry Reedy wrote:
>
> Everyone working on the English-based Python distribution knows the
> order of the 26 English letters.
How does that solve anything?
I just had to decide whether “Jason V. Miller” had to come before or
after “Jay T. Miller” ('Jason' < '
"David Cournapeau":
> Autotools only help for posix-like platforms. They are certainly a big
> hindrance on windows platform in general,
That is why mingw has MSYS.
mingw is not just a gcc port, but also a miniature gnu environment for
windows. MSYS' bash shell allows us to do things like:
$ ./
On Wed, 11 Aug 2010 09:26:56 pm Simon Cross wrote:
> On Wed, Aug 11, 2010 at 4:39 AM, Benjamin Peterson
wrote:
> > Namespace conflict with what? I would prefer "wraps" unless it's
> > standardized as a behavior for all decorators.
>
> Having the original function available as __wrapped__ would be
On Wed, Aug 11, 2010 at 8:45 PM, Antoine Pitrou wrote:
> On Wed, 11 Aug 2010 12:30:40 +1000
> Nick Coghlan wrote:
>>
>> The second (#9396) came up in the context of the new cache decorators
>> added to functools, and allowing applications to choose their own
>> caching strategies. I suggested exp
On Wed, Aug 11, 2010 at 9:26 PM, Simon Cross
wrote:
> On Wed, Aug 11, 2010 at 4:39 AM, Benjamin Peterson
> wrote:
>> Namespace conflict with what? I would prefer "wraps" unless it's
>> standardized as a behavior for all decorators.
>
> Having the original function available as __wrapped__ would
On Wed, Aug 11, 2010 at 4:39 AM, Benjamin Peterson wrote:
> Namespace conflict with what? I would prefer "wraps" unless it's
> standardized as a behavior for all decorators.
Having the original function available as __wrapped__ would be really
cool, although I'm not quite sure what the behaviour
On Wed, 11 Aug 2010 12:30:40 +1000
Nick Coghlan wrote:
>
> The second (#9396) came up in the context of the new cache decorators
> added to functools, and allowing applications to choose their own
> caching strategies. I suggested exposing the original (uncached)
> function, and Raymond suggested
On Wed, Aug 11, 2010 at 12:56 AM, Alexander Belopolsky
wrote:
..
>
> BTW, does anybody know if
>
> Jiba = Jean-Baptiste LAMY ("Jiba")?
Yes that's it. He work on Soya 3d
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
37 matches
Mail list logo
