Re: Is python-django still maintained in DPMT svn?
On 01/28/2014 10:45 PM, Luke Faraone wrote: > I most probably did forget to push; I'll take a look later today. > > Thanks for the poke, Raphaël, and thanks Barry for helping with the > package! I've been lagging on adopting Python3 myself; it'll be great to > have Django removed from the list of blockers for that transition. :) > > -- Luke Hi there, Is there any progress in adding Python 3 support in the Django package? It'd be nice to not wait too long, because currently, without it to support Python 3, there's no other way but to add django-* packages without support for Python 3 as well, which is annoying (I'm having the issue currently with python-django-pyscss). Would you accept that I try to work it out? Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ae6d72.1070...@debian.org
Re: python 3 and django (was: Is python-django still maintained in DPMT svn?)
On 06/28/2014 03:23 PM, Thomas Goirand wrote: > On 01/28/2014 10:45 PM, Luke Faraone wrote: >> I most probably did forget to push; I'll take a look later today. >> >> Thanks for the poke, Raphaël, and thanks Barry for helping with the >> package! I've been lagging on adopting Python3 myself; it'll be great to >> have Django removed from the list of blockers for that transition. :) >> >> -- Luke > > Hi there, > > Is there any progress in adding Python 3 support in the Django package? > > It'd be nice to not wait too long, because currently, without it to > support Python 3, there's no other way but to add django-* packages > without support for Python 3 as well, which is annoying (I'm having the > issue currently with python-django-pyscss). > > Would you accept that I try to work it out? > > Cheers, > > Thomas Goirand (zigo) I just saw that Brian May added some commits in the SVN to add Python3 support to it. :) Brian, what's left to do before the upload? BTW, I saw that you've added some Suggests: for packages which do not exist yet in Debian (like python3-mysqldb, python3-psycopg, python3-flup, and probably some more). Should we try to add Python 3 support to these first? Are they Python 3.4 compatible? Cheers, Thomas -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ae7024.1040...@debian.org
Re: python 3 and django (was: Is python-django still maintained in DPMT svn?)
On 28 June 2014 17:35, Thomas Goirand wrote: > I just saw that Brian May added some commits in the SVN to add Python3 > support to it. :) > > Brian, what's left to do before the upload? > See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736878 Basically everything is done, except I uploaded to DELAYED/10 - I have been told I have should have made a normal non-delayed upload, it will be delayed in NEW anyway. Not yet had a chance to fix this. If it is possible for somebody else to alter the position first, please do so. BTW, I saw that you've added some Suggests: for packages which do not > exist yet in Debian (like python3-mysqldb, python3-psycopg, > python3-flup, and probably some more). Should we try to add Python 3 > support to these first? Are they Python 3.4 compatible? > I basically copied and edited the entries for the Python2 version :-) I personally will need python3-mysqldb, python3-psycopg, and python3-flup (or equivalent). django-south will be included in Django 1.7, and as such will have Python 3 support. They have just released 1.7RC1, so it should be too much longer before 1.7 is released. -- Brian May
Re: Is python-django still maintained in DPMT svn?
On 28 June 2014 17:23, Thomas Goirand wrote: > Is there any progress in adding Python 3 support in the Django package? > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736878 Also see other thread on debian-python, I just replied there. In short, yes. It'd be nice to not wait too long, because currently, without it to > support Python 3, there's no other way but to add django-* packages > without support for Python 3 as well, which is annoying (I'm having the > issue currently with python-django-pyscss). > Yes, that should be possible when this package gets in. Have had similar concerns myself. -- Brian May
Re: python 3 and django (was: Is python-django still maintained in DPMT svn?)
On 28 June 2014 20:43, Brian May wrote: > django-south will be included in Django 1.7, and as such will have Python > 3 support. They have just released 1.7RC1, so it should be too much longer > before 1.7 is released. > Obviously I meant to say "should not be too much longer". I was told that django-south should "sort of work" with Python 3, but probably not much point packaging a python3-django-south. http://south.aeracode.org/ticket/1210 -- Brian May
Re: RFS: oct2py -- GNU Octave to Python bridge
On Sun, Jun 15, 2014 at 9:28 PM, Stuart Prescott wrote: > Dear Josue, > > Thanks for your work so far on oct2py -- Vincent raised a couple of points > about the packages. I see that you addressed the dh-python dependency and > the > typo'd Suggests -- have you had a chance to address his other question > about > the orig tarball? It would be great to see this package in Debian. > > cheers > Stuart > > -- > Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net > Debian Developer http://www.debian.org/ stu...@debian.org > GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 > Hi Stuart, I have fixed the issued that Vincent found. I've commited the changes to the repo. Sadly the current version released by upstream does not work with Octave 3.8 which is the latests version of Octave in Sid. It seems that upstream is working on that [0], I will have the package ready when the issue is closed. Thanks for your interest Cheers -- Josue Ortega Happy Hacking http://josueortega.org PGP key 4096R/AB4AFD3F 2012-08-20 Fingerprint = 7733 B328 D279 5F5B E232 5ADD 0150 9D5C AB4A FD3F
Re: RFS: oct2py -- GNU Octave to Python bridge
On Sat, Jun 28, 2014 at 10:17 AM, Josué Ortega wrote: > On Sun, Jun 15, 2014 at 9:28 PM, Stuart Prescott > wrote: > >> Dear Josue, >> >> Thanks for your work so far on oct2py -- Vincent raised a couple of points >> about the packages. I see that you addressed the dh-python dependency and >> the >> typo'd Suggests -- have you had a chance to address his other question >> about >> the orig tarball? It would be great to see this package in Debian. >> >> cheers >> Stuart >> >> -- >> Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net >> Debian Developer http://www.debian.org/ stu...@debian.org >> GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 >> > > > Hi Stuart, > > I have fixed the issued that Vincent found. I've commited the changes to > the repo. > Sadly the current version released by upstream does not work with Octave > 3.8 which > is the latests version of Octave in Sid. > It seems that upstream is working on that [0], I will have the package > ready when > the issue is closed. > > Thanks for your interest > > Cheers > -- > Josue Ortega > Happy Hacking > http://josueortega.org > PGP key 4096R/AB4AFD3F 2012-08-20 > Fingerprint = 7733 B328 D279 5F5B E232 5ADD 0150 9D5C AB4A FD3F > > Sorry, I forgot the issue link: https://github.com/blink1073/oct2py/issues/40 -- Josue Ortega Happy Hacking http://josueortega.org PGP key 4096R/AB4AFD3F 2012-08-20 Fingerprint = 7733 B328 D279 5F5B E232 5ADD 0150 9D5C AB4A FD3F
Re: RFS: oct2py -- GNU Octave to Python bridge
On Sat, Jun 28, 2014 at 10:51 AM, Stuart Prescott wrote: > > Hi Josué, > > thanks for the follow-up! > > > Sadly the current version released by upstream does not work with Octave > > 3.8 which > > is the latests version of Octave in Sid. > > interesting... I used your package on sid the other day with no issues in > an > ipython notebook. Maybe I was just lucky in the relatively small set of > features that I was using. > > BTW this means that the package isn't running the test suite at build > time... > but from the bug report you linked to, I assume that the test suite doesn't > completely pass in any case. It would be good if you could run the test > suite > at build time, marking the known-failing tests as xfail so that they can > fail > gracefully but any further failures would be caught. That's right, the mentors version has a dh_override_auto_test, I have removed it the version without the override is on http://anonscm.debian.org/viewvc/python-modules/packages/oct2py/ Even better would be to > also add some autopkgtest tests to the package so that the tests can be > run on > ci.debian.net every time a new octave version appears to make sure things > don't break without someone noticing. > I will take your advice, thanks :) > > > It seems that upstream is working on that [0], I will have the package > > ready when > > the issue is closed. > > the upstream bug is closed but I'm not sure how large the patch was to fix > it > or if it would be possible to apply it to 1.3.0. If you're keen, you could > investigate that... but I perfectly understand waiting for upstream to > release > their next version. > Yeah it's closed but I don't see any commits related. I'll be watching the upstream repo if he commits the fix I'll evaluate if it's better apply the patch to 1.3.0 or wait for the next release > > cheers > Stuart > > -- > Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net > Debian Developer http://www.debian.org/ stu...@debian.org > GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 > Cheers -- Josue Ortega Happy Hacking http://josueortega.org PGP key 4096R/AB4AFD3F 2012-08-20 Fingerprint = 7733 B328 D279 5F5B E232 5ADD 0150 9D5C AB4A FD3F
Re: RFS: oct2py -- GNU Octave to Python bridge
Hi Josué, thanks for the follow-up! > Sadly the current version released by upstream does not work with Octave > 3.8 which > is the latests version of Octave in Sid. interesting... I used your package on sid the other day with no issues in an ipython notebook. Maybe I was just lucky in the relatively small set of features that I was using. BTW this means that the package isn't running the test suite at build time... but from the bug report you linked to, I assume that the test suite doesn't completely pass in any case. It would be good if you could run the test suite at build time, marking the known-failing tests as xfail so that they can fail gracefully but any further failures would be caught. Even better would be to also add some autopkgtest tests to the package so that the tests can be run on ci.debian.net every time a new octave version appears to make sure things don't break without someone noticing. > It seems that upstream is working on that [0], I will have the package > ready when > the issue is closed. the upstream bug is closed but I'm not sure how large the patch was to fix it or if it would be possible to apply it to 1.3.0. If you're keen, you could investigate that... but I perfectly understand waiting for upstream to release their next version. cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201406290251.08066.stu...@debian.org
Re: ITP persistent and merging zope and python teams?
On Jun 27, 2014, at 12:06 PM, Arnaud Fontaine wrote: >I'm not really active lately but I think it would be a good idea to move >most of packages (the ones listed by Brian in his previous email seems >fine to me) to DPMT. Note that there appears to be 48 packages maintained by the Zope team: http://qa.debian.org/developer.php?login=pkg-zope-developers%40lists.alioth.debian.org&comaint=yes I'm not so sure about zope2.12 and zope2.13 but it looks like most of the others could be moved over to DPMT. >BTW, even if this document is not up-to-date, we used to target ZTK >version: https://wiki.debian.org/Zope/ZTK . Shall we keep doing that? That's a good question. I've been using the assumption that if it's available on PyPI, then it must be blessed for general purpose use. Maybe that's a bad assumption. Even the ZTK trunk page is out of date: http://docs.zope.org/zopetoolkit/releases/overview-trunk.html since at least I know that most of the latest versions on PyPI now support Python 3.4. Are either the Debian wiki or the docs.zope.org pages still relevant? We still haven't heard from Gediminas yet, so I think we should wait a little longer. Should we ask for opinions on debian-devel or just let them know once/if the deed is done? -Barry signature.asc Description: PGP signature
What happened to python-defusedxml?
Hello, I'd like to add python3 support to the defusedxml package. However, even though "apt-get source" says that NOTICE: 'defusedxml' packaging is maintained in the 'Svn' version control system at: svn://anonscm.debian.org/svn/python-modules/packages/defusedxml/trunk/ .. there is actually no *defusedxml* module anywhere in python-modules/packages. Can someone tell me what the status of this package is (and how I can help to add python3 support)? Best, Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87wqc0dcit@vostro.rath.org
