You cannot post messages because only members can post, and you are not currently a member.
Description:
Discussion about the Piston mini-framework for creating APIs in Django
|
|
|
Status of django-piston
|
| |
Howdy folks - I do apologize for the inauspicious beginning to my maintainership. I had expected far more of my time to be available from my company to work on Piston, and that didn't happen. Other than the YAML security issue, little has been done since I took the helm. But that does little to change that there's quite a backlog of issues. The last official release doesn't work with the CSRF framework and the current trunk release doesn't work with Django 1.4. On top of that, there are a pile of outstanding issues, bugs, and enhancements in the issue tracker.... more »
|
|
Namespacing
|
| |
Howdy, folks - Piston employs a particular feature of setuptools that declares a package namespace. Ordinarily, you can't install two packages that utilize the same python namespace. With this feature of setuptools and as it's configured for Piston, you could theoretically make your own installable python package that installed itself in the piston.my_cool_extension namespace and setuptools would be happy to read piston.* from the piston package and piston.my_cool_extension.* from your package.... more »
|
|
|