unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: Brett Gilio <brettg@gnu.org>
Cc: 42456@debbugs.gnu.org
Subject: [bug#42456] [PATCH] gnu: Rename python-hy to hy.
Date: Sat, 25 Jul 2020 09:44:32 -0600	[thread overview]
Message-ID: <08f72489-fb0b-c367-ff9e-6cb3beb4e127@gmail.com> (raw)
In-Reply-To: <87a6zo5rdq.fsf@gnu.org>

Though I do not know much about hy, I do know the following:

- There are some libraries written in hy[0].

- There are tools written in hy specifically designed to handle hy.[1]

- Some hy libraries contain macros that I don't think compile into 
python. It looks at first glance like hyclib[2] and hyiter[3] are 
examples of such packages, though I have not confirmed.

- The libraries and programs I have found written in hy look like they 
would use python-build-system. If we see patterns in defining these 
packages, we can always provide a hy-build-system for convenience.

[0]https://libraries.io/search?languages=Hy

[1] https://libraries.io/github/hylang

[2] https://libraries.io/pypi/hyclb

[3]https://libraries.io/pypi/hyiter

On 7/24/20 7:13 PM, Brett Gilio wrote:
> we should justify moving Hy perhaps to its own module. I am
> not overly familiar with Hy, I know that it uses and is compatible with
> Python libraries (as Hy is mostly just sugar on-top of the Python
> runtime) but do Hy-specific libraries exist? If so, I think that would
> make the case for moving Hy to its own module even stronger.




  reply	other threads:[~2020-07-25 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  6:09 [bug#42456] [PATCH] gnu: Rename python-hy to hy Jesse Gibbons
2020-07-21 19:26 ` Jesse Gibbons
2020-07-25  1:13   ` Brett Gilio
2020-07-25 15:44     ` Jesse Gibbons [this message]
2020-07-27 14:40       ` zimoun
2020-07-27 23:05         ` Jesse Gibbons
2020-07-28  2:17           ` zimoun
2020-07-28  4:50             ` Jesse Gibbons
2020-07-28  9:51               ` zimoun

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=08f72489-fb0b-c367-ff9e-6cb3beb4e127@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=42456@debbugs.gnu.org \
    --cc=brettg@gnu.org \
    /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).