Hi simon,
On +2019-11-29 15:12:49 +0100, zimoun wrote:
> Hi Bengt,
>
> On Fri, 29 Nov 2019 at 14:42, Bengt Richter wrote:
>
> > > And what do we win? More reproducibility? More bootstrappability?
> >
> > https://en.wikiquote.org/wiki/C._A._R._Hoare#The_Emperor's_Old_Clothes
> >
> > The first
Hi Bengt,
On Fri, 29 Nov 2019 at 14:42, Bengt Richter wrote:
> > And what do we win? More reproducibility? More bootstrappability?
>
> https://en.wikiquote.org/wiki/C._A._R._Hoare#The_Emperor's_Old_Clothes
>
> The first quote in particular ;-)
I agree with the quote. :-)
But it does not answer
Hi zimoun,
On +2019-11-29 12:41:43 +0100, zimoun wrote:
> Hi Bengt,
>
[...]
>
> > > > That's yet another question: could we patch the upstream code to replace
> > > > Python by something else that's more convenient for Guix. That may
> > > > actually be a worthwhile approach to reduce software
Hi Bengt,
On Fri, 29 Nov 2019 at 07:54, Bengt Richter wrote:
> > For example, considering rust, it is about the bootstrappability. See [1].
> >
> > [1] http://guix.gnu.org/blog/2018/bootstrapping-rust/
> >
>
> That looks horrible to me :)
> Don't they have a "guild disasseble" kind of thing
Hi Konrad
On Fri, 29 Nov 2019 at 08:38, Konrad Hinsen wrote:
> Nice discussion, please go on. With Simon taking the pragmatic point of
> view ("what can we do right now?") and Bengt the long-term idealist
> perspective ("where should Guix be going?"), we might end up getting
> both ends right.
Hi Bengt,
On Fri, 29 Nov 2019 at 07:07, Bengt Richter wrote:
> > Is it not cheap to replace the python2 dependency by the python3 one
> > and try to locally build?
> >
>
> The first step is probably cheap, but if you just s/python2/python3/g
> and it "works," what do you know? Can you even
Hi Bengt and Simon,
Nice discussion, please go on. With Simon taking the pragmatic point of
view ("what can we do right now?") and Bengt the long-term idealist
perspective ("where should Guix be going?"), we might end up getting
both ends right.
Bengt Richter writes:
> The first step is
Hi zimoun,
On +2019-11-27 18:28:36 +0100, zimoun wrote:
> Hi,
>
> On Tue, 26 Nov 2019 at 22:52, Bengt Richter wrote:
>
> > egrep -oh '^[^@;]+' py2eol.txt|sort|uniq -c|sort -h|tail
> > --8<---cut here---start->8---
> > 1 zziplib
> > 2 ffmpeg
> >
Hi zimoun,
On +2019-11-27 18:35:42 +0100, zimoun wrote:
> Hi Konrad,
>
> On Wed, 27 Nov 2019 at 08:56, Konrad Hinsen
> wrote:
>
> > > IOW, a bunch just differ by version -- I wonder how many of the
> > > packages that drew in old versions could run fine with respective
> > > latest versions
Hi Konrad and Hartmut,
This is great!
On Thu, 28 Nov 2019 at 18:24, Hartmut Goebel
wrote:
> I've put this into a ehterpad, so we can collaboratively work on this,
> without doing duplicate work, and add comments:
>
> https://annuel.framapad.org/p/guix-python2-eol?lang=en
I am proposing to
Am 28.11.19 um 15:40 schrieb Konrad Hinsen:
> Konrad Hinsen writes:
>
>> I'd say the very first thing we should do is look at all non-Python
>> packages that depend indirectly on Python 2.
> Here comes an update of my Python-2-in-Guix analysis. Sorted output,
> distinction between likely
Konrad Hinsen writes:
> I'd say the very first thing we should do is look at all non-Python
> packages that depend indirectly on Python 2.
Here comes an update of my Python-2-in-Guix analysis. Sorted output,
distinction between likely libraries and likely application packages.
Plus the list of
zimoun writes:
>> It would be a shame if half a dozen lines of python were pulling in
>> all that weight if it could have been a few lines of guile or bash instead.
>
> Do you propose to patch each time? Because I am not convinced again
> that upstream will change Python to Guile.
We have
Hi,
On Wed, 27 Nov 2019 at 09:36, Konrad Hinsen wrote:
> > I assume many of these package can be updated. (Indeed I just updated
> > pdfposter, which I'm maintaining.)
>
> Great. That's the kind of response I was hoping for!
Nice!
On lost time (building, boring meeting, etc.) I will pick one
Hi Konrad,
On Wed, 27 Nov 2019 at 08:56, Konrad Hinsen wrote:
> > IOW, a bunch just differ by version -- I wonder how many of the
> > packages that drew in old versions could run fine with respective
> > latest versions of what they are dependent on?
>
> That's a very good question!
Is it not
Hi,
On Tue, 26 Nov 2019 at 22:52, Bengt Richter wrote:
> egrep -oh '^[^@;]+' py2eol.txt|sort|uniq -c|sort -h|tail
> --8<---cut here---start->8---
> 1 zziplib
> 2 ffmpeg
> 2 ghc
> 2 openimageio
> 3 bedtools
> 5 mozjs
>
Hi Hartmut,
> I assume many of these package can be updated. (Indeed I just updated
> pdfposter, which I'm maintaining.)
Great. That's the kind of response I was hoping for!
> bypthon2 and ptpython2 are REPLs for python2 - bypthon and ptpython are
> the resp. packages for python3.
There are a
Hi Bengt,
> IOW, a bunch just differ by version -- I wonder how many of the
> packages that drew in old versions could run fine with respective
> latest versions of what they are dependent on?
That's a very good question!
> It would be really interesting if you could tweak your
Hi Konrad,
On +2019-11-26 17:51:52 +0100, Konrad Hinsen wrote:
> Konrad Hinsen writes:
>
> > I'd say the very first thing we should do is look at all non-Python
> > packages that depend indirectly on Python 2.
>
> Here is an attempt at identifying them:
>
>
getmail is still python2.7, but on the mailinglist of it
(not archived iirc) there are efforts to move it to python3-only,
however this will take time. I've looked into porting it before
and half-succeeded (only half due to the same problem as the
maintainer has: time).
I think i saw getmail on
Hi Konrad,
Am 26.11.19 um 17:51 schrieb Konrad Hinsen:
> I find 313 packages (see list below). A few of them are still Python
> stuff (has "python" in the name but not "python2"), but most of them
> look like packages that are not themselves Python libraries.
Thanks for having brought up this
Konrad Hinsen writes:
> I'd say the very first thing we should do is look at all non-Python
> packages that depend indirectly on Python 2.
Here is an attempt at identifying them:
;;
(use-modules (guix packages)
(gnu packages)
On Thu, Nov 21, 2019, at 11:46 AM, zimoun wrote:
> What do you do?
> Do we deprecate the python2 packages? If yes, what would be the
> schedule? If no, do we move all the python2 packages to a
> python2-xyz.scm file?
> Do we do nothing? Based on what rationale?
I think a good place to start is by
Hi Simon,
> What do you do?
Well, me, personally, I continue to do most of my research using Python 2
because I cannot afford to port everything to Python 3. And since I do
only number crunching, meaning nothing with security implications, I am
not particularly worried.
> Do we deprecate the
Dear,
The end-of-life of Python 2 is coming...
https://www.python.org/doc/sunset-python-2/
https://www.python.org/dev/peps/pep-0373/
Projects pledge to drop their support of Python 2.
https://python3statement.org/
What do you do?
Do we deprecate the python2 packages? If yes, what would
Dear,
The Python 2 end-of-life is coming...
What is the schedule to deprecate the python2 packages?
All the best,
simon
26 matches
Mail list logo
