Custom Query (121 matches)
Results (79 - 81 of 121)
| Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #6 | fixed | pyyaml 3000 is not in the Python cheese shop | xi | dholth@… | |||||||||||||||||||||||||||
| Description |
Also consider this word of wisdom from PEP 8: "Modules should have short, lowercase names, without underscores." Thanks! |
||||||||||||||||||||||||||||||
| #42 | wontfix | List objects are unhashable | xi | dfnord@… | |||||||||||||||||||||||||||
| Description |
Even though yaml specification allows lists ("flow collections on yaml jargon") to be keys, pyaml fails to use them, as lists are unhashable. For instance, loading "[1, 2]: something" gives the error "found unacceptable key (list objects are unhashable)" As a away around this, flow collections could be translated into a simple hasheable subclass of list, such as: class HasheableList(list):
#############################
## Public Methods
#############################
def __hash__(self):
return hash(tuple(self))
|
||||||||||||||||||||||||||||||
| #71 | wontfix | libyaml does not build with MinGW | xi | clive.crous@… | |||||||||||||||||||||||||||
| Description |
I'm unable to build libyaml under MinGW due to assumtions within the source code that "WIN32" means Visual Studio. I use gcc, even in windows. Simple patch to yaml.h#260 fixes this =>
Thanks, Clive |
||||||||||||||||||||||||||||||
