xml bug?

[Imbaud Pierre]

Erik Johnson a écrit :
> "Imbaud Pierre" <pierre.imbaud at laposte.net> wrote in message
> news:4594130c$0$318$426a74cc at news.free.fr...
> 
>>Now my points are:
>>- how do I spot the version of a given library? There is a __version__
>>   attribute of the module, is that it?
> 
> 
> Yes, the module maintainer should be incrementing this version for each new
> release and so it should properly correspond to the actual revision of code.
> 
> 
>>- How do I access to a given library buglist? Maybe this one is known,
>>   about to be fixed, it would then be useless to report it.
> 
> 
> Not exactly sure, but this is probably a good place to start:
> http://docs.python.org/modindex.html
But python.org was the right entry point, it sent me to the bug
tracker: http://sourceforge.net/tracker/?group_id=5470&atid=105470
Its a bit short on explanations... And I found unsolved issues,
3 years old! this indexes the modules, not the buglist!

> 
> 
>>- How do I report bugs, on a standard lib?
> 
> 
> I found this link:
> 
> http://sourceforge.net/tracker/?group_id=5470&atid=105470
Right! Same place to fetch and to submit. Fair.
> 
> by looking under the "help" item at www.python.org (an excellent starting
> place for all sorts of things).
> 
> 
>>- I tried to copy the lib somewhere, put it BEFORE the official lib in
>>   "the path" (that is:sys.path), the stack shown by the traceback
>>   still shows the original files being used. Is there a special
>>   mechanism bypassing the sys.path search, for standard libs? (I may
>>   be wrong on this, it seems hard to believe...)
> 
> 
> My understanding is sys.path is searched in order. The first entry is
> usually the empty string, interpreted to mean the current directory. If you
> modify sys.path to put the directory containing your modified code in front
> of where the standard library is found, your code should be the one used.
> That is not the case?
I put it in front, as for the unix PATH...
> 
> 
>>- does someone know a good tool to validate an xml file?
> 
> 
> Typing "XML validator" into google returns a bunch. I think I would start
> with the one at w3.org:  http://validator.w3.org/
> 
> 
Ill try this. Thanks a lot, my friend!