unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 38554@debbugs.gnu.org
Subject: [bug#38554] [PATCH 4/5] Add python2-fastentrypoints
Date: Sun, 15 Dec 2019 17:37:15 -0700	[thread overview]
Message-ID: <f5ee2fb730c9a0ba53317480202fcb4350dec9db.camel@gmail.com> (raw)
In-Reply-To: <CAJ3okZ3uiZbVYK5UorUPEn9NdwyKu8mbDhdywT2VxgwbtscNeQ@mail.gmail.com>

On Thu, 2019-12-12 at 18:18 +0100, zimoun wrote:
> Hi Jesse,
> 
> Thank you for your patches.
> 
> As you have maybe seen, I have file a bug [1] to track the Python
> packages and the end-of-file of Python 2. Here you add a new Python 2
> entry. My question is: do we absolutely need it?
> 
> I have seen your bug report about the broken Hy REPL and this series
> fixes it. My question is just: can we continue to add
> `package-with-python2` packages?
> 
> 
> All the best,
> simon
> 
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38420
This concern is why I added the python2 packages in separate patches
contrary to tradition. I wanted to know what others thought of it. We don't
necessarily need to add the python2 packages, especially when the repository
says this will be the last version of hy to support python2 and those
packages are only added to support hy in python2. I recommend you start a
discussion with Brett, who reviewed the patches and told me to combine patch
1 with 4 and 2 with 5. 
I have too much going on to create and send updated patches before Tuesday,
so I guess now is the time for such discussion.

  reply	other threads:[~2019-12-16  0:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  2:29 [bug#38554] [PATCH 0/5] Update python-hy to 0.17.0 Jesse Gibbons
2019-12-10  2:35 ` [bug#38554] [PATCH 1/5] Add python-fastentrypoints Jesse Gibbons
2019-12-10  2:36 ` [bug#38554] [PATCH 2/5] Add python-funcparserlib Jesse Gibbons
2019-12-10  2:37 ` [bug#38554] [PATCH 3/5] Update python-hy to 0.17.0 Jesse Gibbons
2019-12-10  2:37 ` [bug#38554] [PATCH 4/5] Add python2-fastentrypoints Jesse Gibbons
2019-12-12 17:18   ` zimoun
2019-12-16  0:37     ` Jesse Gibbons [this message]
2019-12-10  2:38 ` [bug#38554] [PATCH 5/5] Add python2-funcparserlib Jesse Gibbons
2019-12-10  4:25 ` [bug#38554] [PATCH 0/5] Update python-hy to 0.17.0 Brett Gilio
2019-12-10 21:59   ` Jesse Gibbons
2019-12-12 17:23     ` zimoun
2019-12-21 17:14 ` [bug#38554] [PATCH v2 1/3] gnu: Add python-fastentrypoints Jesse Gibbons
2019-12-21 17:14 ` [bug#38554] [PATCH v2 2/3] gnu: Add python-funcparserlib Jesse Gibbons
2019-12-21 17:14 ` [bug#38554] [PATCH v2 3/3] gnu: python-hy: Update to 0.17.0 Jesse Gibbons
2019-12-25  7:27   ` bug#38554: " Brett Gilio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5ee2fb730c9a0ba53317480202fcb4350dec9db.camel@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=38554@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).