Override component to main
django-piston3 0.3~rc2-3ubuntu1 in xenial: universe/python -> main
python-django-piston3 0.3~rc2-3ubuntu1 in xenial amd64:
universe/python/optional/100% -> main
python-django-piston3 0.3~rc2-3ubuntu1 in xenial arm64:
universe/python/optional/100% -> main
OK, I understand that the bugs I mentioned were inherited problems that
you're working on. Having them there a little longer won't make main
any worse. (Though I believe the duplicate oauth and decorator bits are
recent regressions? We used to have a delta to add the build-deps.)
But please
Please not that current piston in the UBuntu archive (the python2
version) also doesn't not use python-decorator and uses the one it
ships. On that basis, the current piston in main would be exactly the
same as the piston we are trying to get in main, with the difference of
the python3 related
With our alpha due out this week, we'd like to postpone migrating to
python-decorator to post-func-freeze. Bug #1546236 filed as a critical
bug to make that transition
** Changed in: django-piston3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
oauth (1) isn't a simple change to use python-oauth, and (2) needs to
migrate to python-oauthlib (bug 1118815, and 1546216) Considered
critical for xenial, with MAAS as the assigned bug team.
decorator: testing that change now.
1546215 is the bug number for fixing tests.
Debian/copyright
The MAAS team commits to the maintenance of piston3.
--
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:
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
