Re: The python command in Debian

2020-07-18 Thread Rene Engelhard
Hi, Am 14.07.20 um 11:00 schrieb Piotr Ożarowski: > FTR: I didn't change my mind. /usr/bin/python is still used outside > Debian packages, in /usr/local/bin scripts and applications and I > strongly disagree to touch it. Unfortunately (at least if I remember correctly I came up with an example

Re: Bug#949187: transition: python3.8

2020-02-05 Thread Rene Engelhard
On Wed, Feb 05, 2020 at 01:26:31PM +, Simon McVittie wrote: > On Wed, 05 Feb 2020 at 08:18:41 +0100, rene.engelh...@mailbox.org wrote: > > Thanks, yes, that prevents the install of the "old" > > gobject-introspection with the new python3 from experimental. > > Sorry, I wasn't thinking

Re: Bug#949187: transition: python3.8

2020-02-04 Thread rene . engelhard
Hi, Am 4. Februar 2020 23:27:13 MEZ schrieb Simon McVittie : >On Tue, 04 Feb 2020 at 21:20:07 +0100, Rene Engelhard wrote: >> root@frodo:/# g-ir-scanner >... >> ModuleNotFoundError: No module named 'giscanner._giscanner' > >This is fixed in 1.62.0-5 (#950267). Th

Re: Bug#949187: transition: python3.8

2020-02-04 Thread Rene Engelhard
s accidentially kept disabled after a python3.8 test rebuild... * re-enable building of the "test packages" (-smoketest-data, -subsequentcheckbase) -- Rene Engelhard Sun, 15 Dec 2019 10:29:19 + happened.) Regards, Rene

Re: Bug#949187: transition: python3.8

2020-02-02 Thread Rene Engelhard
On Sun, Feb 02, 2020 at 06:12:08PM +0100, Rene Engelhard wrote: > Hi, > > On Sun, Feb 02, 2020 at 06:07:29PM +0100, Matthias Klose wrote: > > > e.g. fontforge is still red in > > > https://release.debian.org/transitions/html/python3.8.html. > > > > >

Re: Bug#949187: transition: python3.8

2020-02-02 Thread Rene Engelhard
Hi, On Sun, Feb 02, 2020 at 06:07:29PM +0100, Matthias Klose wrote: > > e.g. fontforge is still red in > > https://release.debian.org/transitions/html/python3.8.html. > > > > That means that a rebuild of stuff using fontforge in the build will > > just FTBFS since it will be called with

Re: Bug#949187: transition: python3.8

2020-02-02 Thread Rene Engelhard
On Sun, Feb 02, 2020 at 05:53:37PM +0100, Rene Engelhard wrote: > On Sun, Feb 02, 2020 at 09:35:04AM +0100, Matthias Klose wrote: > > > On 17-01-2020 23:28, Matthias Klose wrote: > > >> Please add a transition tracker to switch the python3 default to 3.8. > >

Re: Bug#949187: transition: python3.8

2020-02-02 Thread Rene Engelhard
On Sun, Feb 02, 2020 at 09:35:04AM +0100, Matthias Klose wrote: > > On 17-01-2020 23:28, Matthias Klose wrote: > >> Please add a transition tracker to switch the python3 default to 3.8. > >> It's not > >> yet ready, however it would be good to see affected packages. Please copy > >> it > >>

Re: Status Update For Bug#798999: transition: python3.5 supported

2015-10-12 Thread Rene Engelhard
Hi, On Mon, Oct 12, 2015 at 10:24:02AM -0400, Scott Kitterman wrote: > Additionally, looking ahead to the next transition that makes python3.5 the > default python3, it would be good to look at the packages that build-dep on > python3-dev and see if it's reasonable to have them build-dep on

Re: Q: Python 2 vs Python 3 and wxgtk2.8 vs wxgtk3.0

2014-07-07 Thread Rene Engelhard
[ I filed the bug against GNUmed to migrate to python3. Dropping that bug in my reply since it has NOTHING to do with the real bug. At least a new bug wxwidgets should provide a python3 package then blocks the gnumed bug, but it's not something one should handle there ] Hi, On Mon, Jul 07, 2014

Re: (again) Why default python is not 2.6 yet?

2010-03-01 Thread Rene Engelhard
Hi, On Wed, Feb 17, 2010 at 04:18:28PM +0100, Sandro Tosi wrote: That holds true any time we do the switch. So when should we change the default? the moment we freeze? From my personal POV you csn do now, I think the release team would not agree, though ;-) Grüße/Regards, René -- .''`.

Re: (again) Why default python is not 2.6 yet?

2010-02-17 Thread Rene Engelhard
Hi, On Wed, Feb 17, 2010 at 12:05:56AM +0100, Sandro Tosi wrote: If there is a valid, technical reason, please let us know, but as of now I can't see any. Loads of RC bugfixes (partly on obsolete versions) waiting to enter testing which would more blocked that it already is with the mips*

Re: (again) Why default python is not 2.6 yet?

2010-02-17 Thread Rene Engelhard
Hi, On Wed, Feb 17, 2010 at 04:18:28PM +0100, Sandro Tosi wrote: On Wed, Feb 17, 2010 at 15:49, Rene Engelhard r...@debian.org wrote: On Wed, Feb 17, 2010 at 12:05:56AM +0100, Sandro Tosi wrote: If there is a valid, technical reason, please let us know, but as of now I can't see any

Re: Bug#520944: [python-uno] Python support in OpenOffice is completely broken

2009-03-23 Thread Rene Engelhard
tag 520944 + confirmed tag 520944 + help thanks { CC'ing debian-python } Hi, Adrià Cereto Massagué wrote: the problem seems to be specifically in the module pyuno. Here's the traceback in an interactive python shell: Python 2.5.4 (r254:67916, Feb 18 2009, 03:00:47) [GCC 4.3.3] on

Re: Python 2.1/2.2 removal; Python 2.4 as default

2006-04-11 Thread Rene Engelhard
Matthias Klose wrote: Jeroen van Wolffelaar writes: The first freezes are already closing in fast, did I miss something? There's no update since http://lists.debian.org/debian-devel-announce/2005/10/msg4.html Yes. At least the January, 3rd one

Re: PyUno availability

2004-07-25 Thread Rene Engelhard
[ -python is the wrong list. pxuno is an OOo component and built from OOo so -openoffice would be appropriate ] Hi, Encolpe DEGOUTE wrote: the extension PyUno of the openoffice debian package has been compiled with system python. That's a good thing, but I can't import the « uno » module.