ays back though -- yesterday, the online doc was
still complete: I believe it was last built on March the 28th. Yours,
--
Sylvain Fourmanoit
Memory fault -- core...uh...um...core... Oh dammit, I forget!
___
Python-Dev mailing list
Python-Dev@
On Sat, 13 Dec 2008, Guido van Rossum wrote:
If you reindent, much of the history of the file is essentially lost --
"svn blame" will blame whoever reindented the code, and it's a pain to
go back.
I am not a subversion specialist, but it appears this part can be handled
gracefully by passing
Armin Rigo wrote:
> In the same spirit, maybe it could be slightly re-oriented towards a
> dumper/loader for more than config files; for example, it could provide
> a safe inverse of repr() for common built-in types
New version of miniconf (version 1.2.0) is out [1][2], including a
unrepr() fun
An updated version is now available, based to the feedback of Phillip J.
Eby and David Hopwood (stand-alone module[1], patch[2]):
- the module is now reentrant
- the sloppy case with Name nodes is now covered properly
- the node lookup procedure was optimized, leading to a 20% speed
increase on
> It looks like it's trivial to fix; the code uses a strange and
> unnecessary complication of creating nested classes and nested
> singleton instances thereof. Getting rid of the singletons to create a
> new instance for each dump/load call would suffice to make the
> implementation re-entran
> miniconf, OTOH, appears to have an interface compatible with capability
> security (I have not checked that the compiler.ast module used in its
> implementation is safe.)
I woudn't be 100% sure either (obviously, I didn't write this nice piece
of code, let alone the underlying parser), but I re
I wrote a data persistence module called miniconf, aimed at making
easy to create and safely retrieve configuration info from external,
human-readable sources using Python syntax. I feel it would eventually
make a nice addition to the standard library.
The code was only newly refactored in this
