Re: [PATCH 01/17] gnu: Add python-atomicwrites.

[Leo Famulari]

On Thu, Jan 07, 2016 at 11:48:57AM -0500, Leo Famulari wrote:
> On Wed, Jan 06, 2016 at 09:02:10PM +0200, Efraim Flashner wrote:
> > On Sun,  3 Jan 2016 19:04:59 -0500
> > Leo Famulari <address@hidden> wrote:
> > 
> > > * gnu/packages/python.scm (python-atomicwrites): New variable.

[...]

> > Is this python 3 only?
> 
> The upstream developer has communicated that they intend to officially
> stop supporting Python 2 [0] in the software that uses this library. And
> I think have already stopped supporting it unofficially [1].
> 
> So based on [0] I didn't include a python-2 package variant. If somebody
> wants one, I can ask upstream if it's supported for this library.

I asked [0] and he does intend to continue supporting Python 2 in this
and in python-click-log.

However, the Python 2 variants require python2-setuptools. Since they
can't be automatically translated, I believe that when trying to use
them, we will hit the same issue as in #22013 [1]. Is that right?

If there is no user of the Python 2 variants, I see no reason to include
them until the problem in that bug is resolved, if it applies here.

[0]
https://github.com/untitaker/vdirsyncer/issues/316#issuecomment-169734694

[1]
http://debbugs.gnu.org/db/22/22013.html