Skip to content
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

Open
ioverka opened this issue Apr 5, 2016 · 5 comments
Open

Changes to imeji REST API v1 #21

ioverka opened this issue Apr 5, 2016 · 5 comments

Comments

@ioverka
Copy link
Contributor

ioverka commented Apr 5, 2016

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.

ioverka pushed a commit to ioverka/pyimeji that referenced this issue Apr 5, 2016
@ioverka
Copy link
Contributor Author

ioverka commented Apr 5, 2016

For now, a simple workaround is available in the patch listed above. A more comprehensive fix might be committed later.

@xrotwang
Copy link
Contributor

xrotwang commented Apr 6, 2016

@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.

@ioverka
Copy link
Contributor Author

ioverka commented Apr 6, 2016

@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"?)

@xrotwang
Copy link
Contributor

xrotwang commented Apr 6, 2016

@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.

@natasab
Copy link

natasab commented Apr 6, 2016

@xrotwang once again, thanks a lot for the initial package and transferring the ownership.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants