Custom Query (121 matches)
Results (40 - 42 of 121)
| Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #79 | wontfix | Multiple scalar values used as key creates Python hash error | xi | clay@… | |||||||||||||||||||||||||||
| Description |
The YAML specification suggests that a mapping can have a key made of more than one item, as in ? - Detroit Tigers - Chicago cubs : - 2001-07-23 However, when that data is imported via yaml.load(), PyYAML exits with a yaml.constructor.ConstructorError?, saying "found unacceptable key (list objects are unhashable)" Is there a way to force multi-value keys to be processed as tuples instead of lists? |
||||||||||||||||||||||||||||||
| #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 |
||||||||||||||||||||||||||||||
| #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))
|
||||||||||||||||||||||||||||||
