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
Great work on bringing restless a bit more up to date.
Have you spoken to @toastdriven about perhaps taking over maintenance of restless? Daniel is a great member of the Python community and may be open to assistance maintaining his package, especially since other similar projects of his have successfully found new homes in the past couple of years.
If that isn't an option or your preference, is there any chance you could identify the key areas where care should be taken when migrating a project from restless to restkiss? I have a very simple restless project I'd like to update to be Django 1.10 compatible, but wouldn't mind a little bit of info on what you've changed since forking.
Thanks again for your work on this little project :)
The text was updated successfully, but these errors were encountered:
We tried to contact @toastdriven a few months ago to take over the library in an official fashion (including its PyPI entry), but he has not answered to this day - hence the name change.
Otherwise, apart from the name restkiss is a drop-in replacement; release v2.0.2 was made mostly of accumulated bugfixing and error handling. Two places benefited from some extra flexibility, however:
The default URL routes, which now accept lowercase letters and dashes as well, making it possible to handle UUIDs, slugs and hashes out-of-the-box.
HttpError and its children; many more subclasses were added (including the somehow missed Forbidden) and Resource doesn't try to stringify its contents anymore, so any serializable object is fair game.
@ElSaico You have my apologies. I did not see your original email(s?). I'd actually rather not fork & grant you access to the official repo instead. If you are willing, please email me again & I can respond at length as well as get you access.
The tl;dr on why I never saw the original is: Life has been pretty bad & I've had to mostly ignore OSS. I wasn't expecting restless to get the traction it did. :(
Great work on bringing restless a bit more up to date.
Have you spoken to @toastdriven about perhaps taking over maintenance of
restless
? Daniel is a great member of the Python community and may be open to assistance maintaining his package, especially since other similar projects of his have successfully found new homes in the past couple of years.If that isn't an option or your preference, is there any chance you could identify the key areas where care should be taken when migrating a project from
restless
torestkiss
? I have a very simple restless project I'd like to update to be Django 1.10 compatible, but wouldn't mind a little bit of info on what you've changed since forking.Thanks again for your work on this little project :)
The text was updated successfully, but these errors were encountered: