-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
entry.parentgroup doesn't work for history entries #122
Comments
BTW: the representation of the items under python3 looks a bit strange, the leading "b" should not be part of the representation but indicate a type, but I'm no specialist |
I have a possible solution and some tests at https://github.com/BoomerB/pykeepass |
I agree with this. The issue is the May deserve it's own ticket |
@whwright the question is: what type should be returned? is it ok to return an unicode string - which is the default for python3 anyway - or does it have to be a plain string?
if it has to be a plain str, then something like
would do the trick |
There are entries with cyrillic characters in one of the test databases. |
* add test for delete_custom_property * string fixes and python2 FIXMEs * move `first`, `history` into _xpath, use kp._xpath everywhere * clarify return types * move .parentgroup to baseelement.py * use UUID for __eq__, fix #122 * fix for when no attachments present * perform all tests on both kdbx3 and kdbx4
Hi,
I accidentally found the following issue:
same happens with python3
The text was updated successfully, but these errors were encountered: