-
Notifications
You must be signed in to change notification settings - Fork 6
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
Changes to imeji REST API v1 #21
Comments
For now, a simple workaround is available in the patch listed above. A more comprehensive fix might be committed later. |
@ioverka Are you interested in taking over maintenance of pyimeji? I don't use it anymore myself, so keeping up with newer releases of imeji would be a bit difficult to do. |
@xrotwang We assumed that you won't be able to maintain pyimeji any longer (THANKS a lot for your contribution) and currently discuss on how to continue the development internally. Does anything needed to be done to take over the maintenance (z.B. "gibhubseitig"?) |
@ioverka githubseitig everything should be fine - I'm not owner of the imeji-community org anyway. To be able to publish new versions to the python package index, someone would have to create an account to which I could transfer ownership of the package. |
@xrotwang once again, thanks a lot for the initial package and transferring the ownership. |
imeji release 3.2. introduced changes to the JSON format returned by several API requests. Affected are: get items, get collections, get albums, get collection Items, get albums items, see https://github.com/imeji-community/imeji/releases/tag/imeji-3.2.0.0
The corresponding methods of pyimeji are no longer working.
The text was updated successfully, but these errors were encountered: