On Thu, Apr 23, 2015 at 02:52:33PM +0200, Enrico Zini wrote:
> On Mon, Apr 20, 2015 at 11:14:28AM -0400, Paul Tagliamonte wrote:
>
> > So, round one of all of this is getting the critical path *under* each
> > of our services ready, so that when we need to migrate, we don't need
> > to scramble.
>
> There is another constraint that I forgot: the production environment is
> Debian Stable, which will soon mean Jessie. If a python2-only module
> gets ported to python3 in jessie+1, to use it for debian.org services
> the python3 version also needs to be maintained in backports.
Yep! So, my plan that I outlined on d-d-a was to basically attack that --
the depends chains -- first. Since we are doing this before strictly
needed (that is, nearly two cycles out), we can ensure everything is
working and migrated a cycle before we are forced to.
This gives us a relaxing pace and also lets us target things
pragmatically. You're right, and I'd be happy to help with backporting
stuff for services porting to Python 3 as needed, but there's no urgent
rush to move everything over today.
That's the idea behind porting now, so that everything's totally tight.
> For example, I am about to add python-git as a dependency to
> nm.debian.org, as I need it to parse the stream of changes that I get
> via the keyring.debian.org git changelog, and python-git is python2-only
> in Jessie[1]. Having python3-git in jessie+1 won't be enough to make
> nm.debian.org deployable with python3: python3-git will also need to be
> in jessie-backports, and with a commitment to keep it up to date with
> security uploads, because I'm going to run it every night to parse git
> logs that are obtained via potentially insecure network connections.
Aye. Yep.
> Enrico
>
> [1] I've recently been really sad to figure out that python-git is
> python2-only, and so is dulwich. As a personal policy, if I start a
> new python project now I start it with python 3.4. I had to start a
> new project with python2 because of that, and I felt dirty.
Yeah, ditto. I talked with Jelmer about this, there was a patch for Py3,
but it fell too far behind development's trunk. If anyone on the
py3porters wants to do that, it'd seriously help me out too.
Cheers,
Paul
--
.''`. Paul Tagliamonte <paultag@debian.org> | Proud Debian Developer
: :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87
`. `'` http://people.debian.org/~paultag
`- http://people.debian.org/~paultag/conduct-statement.txt
_______________________________________________
py3porters-devel mailing list
py3porters-devel@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel