On Wednesday 15 April 2015 20:54:38 Barry Warsaw wrote:
> I'm up for helping too, of course.
Me too!
Kind regards,
--
Daniele Tricoli 'Eriol'
http://mornie.org
signature.asc
Description: This is a digitally signed message part.
On Apr 16, 2015, at 10:07 AM, Karsten Hilbert wrote:
>Maybe /usr/bin/python can become a wrapper executing Python 2
>(like now) but also showing
>
> Python 2 will be deprecated in 2020 the latest.
> Do not use it to write new code.
> Consider helping in porting existing code.
>
On Apr 16, 2015, at 10:10 AM, Karsten Hilbert wrote:
>With all this desire to drop Python 2 eventually -- there are
>packages, say gnumed-client, which simply cannot be ported to
>Python 3 ATM because important dependencies don't exist for
>Py 3, say pythonX-wxgtk.
Right. The best approach is to
With all this desire to drop Python 2 eventually -- there are
packages, say gnumed-client, which simply cannot be ported to
Python 3 ATM because important dependencies don't exist for
Py 3, say pythonX-wxgtk.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 45
On Wed, Apr 15, 2015 at 04:27:51PM -0400, Paul Tagliamonte wrote:
> I'd like this to have the endorsement of the team, so, does anyone object to
> me asking people to not write new tools in Python 2 only (prefer alternative
> deps or porting), and only use Python 2 in very special curcumstances or
On Thu, Apr 16, 2015 at 4:48 AM, Scott Kitterman wrote:
> You might also ask Debian teams using Python in the Debian infrastructure to
> review their packaged dependencies and identify any that aren't available for
> Python3. We'll need to know that soon so we can work on porting
> dependencies/f
Paul Tagliamonte writes:
> I'll make note of a team which should exist to help with [porting
> packages to Python 3 compatibility], (I'm up to help with this) that
> was one of the items that came out of the PyCon chit-chat.
I have recent experience making code bases Python 2 and Python 3
compat
On Apr 15, 2015, at 04:27 PM, Paul Tagliamonte wrote:
>I'd like this to have the endorsement of the team
Looks like you don't need my +1 but I'll give it anyway. :)
>I'll make note of a team which should exist to help with such porting,
>(I'm up to help with this)
I'm up for helping too, of cou
I am happy to help porting things. I did it for a number of non trivial
packages and happy to do more. It's very soothing experience and better
than knitting & sudoku.
On 15 Apr 2015 2:29 pm, "Paul Tagliamonte" wrote:
> Heyya d-p,
>
> I'd like to send an email to d-d-a asking that project to cons
I was saying the same thing in my head, but as i thought about it, if the
cpython maint team (hi doko) wants it, I don't see why not :)
I phrased it in such a way in my mail that I feel comfortable sending my
draft and then working out details without setting ftpteam policy first
On Apr 15, 2015 6
I'll add a note about that, and talk with the ftpteam to see if we can
implement that policy in NEW.
Mails on the thread seem positive so far, I'll post this to d-d-a when I
get home from YUL to DC tonight.
On Apr 15, 2015 5:07 PM, "Matthias Klose" wrote:
> On 04/15/2015 10:27 PM, Paul Tagliamo
On Wednesday, April 15, 2015 11:07:13 PM Matthias Klose wrote:
> On 04/15/2015 10:27 PM, Paul Tagliamonte wrote:
> > Heyya d-p,
> >
> > I'd like to send an email to d-d-a asking that project to consider no
> > longer creating new Debian tools in Python 2.
> >
> > I'd like this to have the endorse
On 04/15/2015 10:27 PM, Paul Tagliamonte wrote:
> Heyya d-p,
>
> I'd like to send an email to d-d-a asking that project to consider no
> longer creating new Debian tools in Python 2.
>
> I'd like this to have the endorsement of the team, so, does anyone object to
> me asking people to not write n
On 2015-04-15 16:27, Paul Tagliamonte wrote:
> I'd like to send an email to d-d-a asking that project to consider no
> longer creating new Debian tools in Python 2.
Makes sense.
I try to use Py3 whenever possible. Sometimes some libs are still
missing, mainly when upstream is not very active. My
Perfect, thanks, Ian! I'll get a ML for a Python 3 porting SWAT team
together once we make sure no one has a sane technical reason to avoid
this so soon (I don't think there's any)
Thanks, Ian! Excited to work with you!
Paul
On Wed, Apr 15, 2015 at 4:35 PM, Ian Cordasco
wrote:
> On Wed, Apr 15
On Wed, Apr 15, 2015 at 3:27 PM, Paul Tagliamonte
wrote:
> Heyya d-p,
>
> I'd like to send an email to d-d-a asking that project to consider no
> longer creating new Debian tools in Python 2.
>
> I'd like this to have the endorsement of the team, so, does anyone object
> to
> me asking people to
On Wednesday, April 15, 2015 04:27:51 PM Paul Tagliamonte wrote:
> Heyya d-p,
>
> I'd like to send an email to d-d-a asking that project to consider no
> longer creating new Debian tools in Python 2.
>
> I'd like this to have the endorsement of the team, so, does anyone object to
> me asking peop
Heyya d-p,
I'd like to send an email to d-d-a asking that project to consider no
longer creating new Debian tools in Python 2.
I'd like this to have the endorsement of the team, so, does anyone object to
me asking people to not write new tools in Python 2 only (prefer alternative
deps or porting)
18 matches
Mail list logo
