Looking at the history of python-django-piston, I get the need for new
maintainers. And I guess the new maintainer has some history of
updating the package... But it's stopped since October, without an
actual 0.3 release (we're stuck on rc2). Any comment on the viability?
Are we going to see a real 0.3 release?
I know these are sins that we've inherited, but still:
- What's the story with tests? debian/rules says they are broken. How
hard would it be to fix?
- Bundling python-oauth as piston/oauth.py is bad. (A) At a minimum, we
should not install the bundled copy and instead use the system python-
oauth module. (b) But really, we should use python-oauthlib instead
(see bug 1118815)
- Bundling python-decorator as piston/decorator.py is also bad. What's
the story there? Looks like the system module and the bundled module
are different. Are they compatible, such that we can just use the
system one?
Oh and it needs a team bug subscriber for whomever is looking after this
in Ubuntu.
And not a blocker for main (though maybe should have been for NEW), but
debian/copyright's formatting is bad. The long license block needs to
be indented. (And should say BSD-3-clause or whatever instead of just
BSD) (And is Stefan Zimmerman really the only copyright holder for
upstream?)
** Changed in: django-piston3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542325
Title:
[MIR] django-piston3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-piston3/+bug/1542325/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
