You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is probably similar to #9, but was not resolved by the fix. Bug is present in version 0.2.12.
A direct call to Node.attrs results in a segmentation fault. Calling methods on the object is fine, but getting the dict representation directly crashes the Python interpreter. The same does not happen with Node.attributes.
When calling attrs on a temporary instance, the tree may already be
deallocated when the tag name is being retrieved, which causes a null pointer
dereference. This fix doesn't really solve the problem, but at least it
prevents the crash.
Also fixes a bug in items() that made the method useless.
Fixesrushter#39
* Apply `decode_errors` to encoding as well, fixes#40
* Fix __repr__() segfault and buggy items() on _Attributes
When calling attrs on a temporary instance, the tree may already be
deallocated when the tag name is being retrieved, which causes a null pointer
dereference. This fix doesn't really solve the problem, but at least it
prevents the crash.
Also fixes a bug in items() that made the method useless.
Fixes#39
* Add test for unencodable strings
This issue is probably similar to #9, but was not resolved by the fix. Bug is present in version 0.2.12.
A direct call to
Node.attrs
results in a segmentation fault. Calling methods on the object is fine, but getting the dict representation directly crashes the Python interpreter. The same does not happen withNode.attributes
.Repro case:
Also, while
keys()
andvalues()
work fine,items()
is buggy:The text was updated successfully, but these errors were encountered: