Re: Availability of Numpy, WX, Matplotlib and Scipy under Python3
Re: Availability of Numpy, WX, Matplotlib and Scipy under Python3 = Thanks to Thomas Kluyver and Dmitrijs Ledkovs. On Mon, 2012-09-03 at 21:27 +0100, Thomas Kluyver wrote: > Python 3 versions of numpy and scipy are already in wheezy. wx and > matplotlib haven't yet released Python 3 compatible versions, and > Wheezy is frozen now, so they've missed that boat. If you need to use > those packages for a substantial application in the near future, > sticking with Python 2 for now is your safest bet. If you use Python > 2.6 or 2.7 with modern idioms, it should be relatively easy to port > code later when all the libraries are ready. Given the issue with (especially) WX, I think I will stick with Python 2.7 for the time being. On Tue, 2012-09-04 at 01:07 +0100, Dmitrijs Ledkovs wrote: You may want to request a backport from folks who do those, and maybe > (dependencies permitting) they can make a python3 backport of scipy / > numpy for current stable release squeeze. I'll consider that if and when I find any differences between Python 2.7 and 3.* that become pressing issues for me. Otherwise, I suspect that any request for a backport from me will only distract from more useful work for a wider range of users. -- It is a pity that (particulaly) wxPython has missed the Wheezy revision window. When I looked at the various GUIs available in Python, I thought that wxPython was the one with the best combination of advanced facilities and ease of use. Thanks again for the quick and useful responses. Best regards -- Nigel Sedgwick, Cambridge Algorithmica Ltd URL: http://www.camalg.co.uk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1346745609.2391.11.ca...@napier3.camalg.co.uk
Re: Availability of Numpy, WX, Matplotlib and Scipy under Python3
On Sep 04, 2012, at 09:00 AM, Nigel Sedgwick wrote: >Given the issue with (especially) WX, I think I will stick with Python >2.7 for the time being. The only suggestion I'd make is that you write your Python 2 code so that it's easier to port to Python 3 when all your dependencies are available. I'm not sure how many good guides there are out there on writing Python 3-friendly Python 2 code, but you might have a look at http://wiki.ubuntu.com/Python/3 for some hints. I suppose the top recommendations I'd give are: * Target nothing older than Python 2.6 (2.7 is even better) * As much as possible, write common idiom code (possibly using the 'six' library if necessary). * from __future__ import absolute_import, print_function, unicode_literals * Get your bytes vs. strings story straight right from the start. * Use b'' for bytes. * Avoid idioms you know are gone in Python 3, like backticks, dict.iter*() methods, xrange(), etc. Or essentially: write your code as if it were a single code base, dual-compatible code base. Eventually, it will be even if you end up dropping Python 2 support at some point. ;) Cheers, -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120905094639.04d3f...@resist.wooz.org
joining the team
Dear admins, Pleas allow me to join "Python Applications Packaging Team" (PAPT) for co-maintaining "xpra" package. Some time ago I sent my join request using form on Alioth but there were no reply yet. My user name is 'onlyjob-guest' (I'm a DM). Thank you. Regards, Dmitry. signature.asc Description: This is a digitally signed message part.
effects of numpy 1.7.0~b1 on sid
Thank you Sandro for pushing a fresh beta numpy to experimental. I have ran my scriptie to check what effects would that version have on build-dependees in sid (which currently might be well not the latest and greatest versions of packages): http://www.onerussian.com/Linux/deb/logs/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid.summary first FAILED/ok column is when building against sid numpy version 1.6.2-1 and the second one is against 1.7.0~b1. Testing builds against python-numpy_1.7.0~b1-1.dsc aster_10.6.0-1-4.dscFAILED FAILED aster_10.6.0-1-4_amd64.build avogadro_1.0.3-5.dscFAILED ok babel_1.4.0.dfsg-8.dsc ok ok basemap_1.0.3+dfsg-2.dsc ok ok biosig4c++_1.3.0-2.dsc ok ok brian_1.3.1-1.dsc ok ok cfflib_2.0.5-1.dsc ok ok cmor_2.8.0-2.dsc ok ok connectomeviewer_2.1.0-1.dsc ok ok cython_0.15.1-2.dscok FAILED http://www.onerussian.com/Linux/deb/logs/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid/cython_0.15.1-2_amd64.build dballe_5.18-1.dsc ok ok dipy_0.5.0-3.dsc ok ok dolfin_1.0.0-7.dsc FAILED ok flann_1.7.1-4.dsc ok ok fonttools_2.3-1.dscok ok gamera_3.3.3-2.dsc ok ok gdal_1.9.0-3.dsc ok ok getfem++_4.1.1-10.dsc FAILED ok gnudatalanguage_0.9.2-4.dscok ok gnuradio_3.6.1-1.dscFAILED ok guiqwt_2.1.6-4.dsc FAILED ok h5py_2.0.1-2.dsc ok ok joblib_0.6.4-3.dsc ok ok lazyarray_0.1.0-1.dsc ok ok libfreenect_0.1.2+dfsg-6.dsc ok ok libgetdata_0.7.3-6.dsc ok ok libmpikmeans_1.5-1.dsc ok ok libvigraimpex_1.7.1+dfsg1-3.dscok FAILED http://www.onerussian.com/Linux/deb/logs/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid/libvigraimpex_1.7.1+dfsg1-3_amd64.build lintian_2.5.10.1.dscFAILED ok magics++_2.14.11-4.dsc ok ok mathgl_1.11.2-14.dscFAILED ok matplotlib_1.1.1~rc2-1.dsc FAILED ok mayavi2_4.1.0-1.dsc FAILED ok mdp_3.2+git78-g7db3c50-3.dsc ok ok mgltools-bhtree_1.5.6~rc3~cvs.20120206-1.dsc ok ok mgltools-dejavu_1.5.6~rc3~cvs.20120206-1.dsc ok ok mgltools-geomutils_1.5.6~rc3~cvs.20120601-1.dscok ok mgltools-gle_1.5.6~rc3~cvs.20120601-1.dsc ok ok mgltools-molkit_1.5.6~rc3~cvs.20120206-1.dsc ok ok mgltools-opengltk_1.5.6~rc3~cvs.20120601-1.dsc ok ok mgltools-pyglf_1.5.6~rc3~cvs.20120601-1.dscok ok mgltools-sff_1.5.6~rc3~cvs.20120601-1.dsc ok ok mgltools-utpackages_1.5.6~rc3~cvs.20120601-1.dsc ok ok mgltools-vision_1.5.6~rc3~cvs.20120601-1.dsc ok ok mgltools-visionlibraries_1.5.6~rc3~cvs.20120601-1.dsc ok ok mlpy_2.2.0~dfsg1-2.dsc ok ok mmass_5.2.0-2.dsc ok ok model-builder_0.4.1-6.dsc ok ok mpi4py_1.3+hg20120611-1.dscok ok mypaint_1.0.0-1.dscok ok necpp_1.5.0+cvs20101003-2.1.dscok ok neo_0.2.0-1.dscok ok nexus_4.2.1-svn1614-1.dsc FAILED ok nibabel_1.2.2-1.dscok ok nipy_0.2.0-1.dsc ok FAILED http://www.onerussian.com/Linux/deb/logs/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid/nipy_0.2.0-1_amd64.build nitime_0.4-2.dsc ok ok nlopt_2.2.4+dfsg-2.dsc ok ok numexpr_2.0.1-3.dsc FAILED FAILED http://www.onerussian.com/Linux/deb/logs/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid/numexpr_2.0.1-3_amd64.build numm_0.4-1.dsc FAILED ok opencv_2.3.1-11.dscok ok openmeeg_2.0.0.dfsg-5.dsc FAILED ok openopt_0.38+svn1589-1.dsc ok ok pandas_0.8.1-1.dsc ok ok pdb2pqr_1.8-1.dsc ok ok pebl_1.0.2-2.dsc ok ok plplot_5.9.9-5.dsc FAILED ok psignifit3_3.0~bet
