unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: Vinicius Monego <monego@posteo.net>,
	Andreas Reuleaux <rx@a-rx.info>,
	50356@debbugs.gnu.org
Subject: bug#50356: python-hy / python-funcparserlib / tox config file
Date: Wed, 22 Dec 2021 16:00:26 +0100	[thread overview]
Message-ID: <867dbwd6r9.fsf@fsfe.org> (raw)
In-Reply-To: <d9c2affa1db41df6eded5f2fc0640ee15c0efb1f.camel@posteo.net>

Vinicius Monego <monego@posteo.net> writes:

> Em sex, 2021-09-17 às 14:32 +0200, Jelle Licht escreveu:
>> 
>> Hello Andreas,
>> 
>> Andreas Reuleaux <rx@a-rx.info> writes:
>> 
>> > Hi,
>> > 
>> > python-hy fails to install for me - because there are issues with
>> > python-funcparserlib, as I understand (or tox - cf the end of the
>> > log below).
>> > 
>> 
>> It seems the hy and funcparserlib devs are coordinating new releases;
>> perhaps we can resolve this issue by updating both python-
>> funcparserlib
>> and python-hy to their respective 1.0.0 releases once they are out.
>> 
>> - Jelle
>> 
>
> The problem is that funcparserlib 0.3.6 (which is the most recent
> release at the moment) is incompatible with the Python version in Guix.
> There is an alpha for funcparserlib 1.0.0 in PyPI. I updated to this
> and Hy to 0.20.0 and it does work aside from 3 Hy tests failing (from a
> total of 621).

The develpoers of hy also have a 1.0a3 alpha release; does your package
of funcparserlib work with that?

> The developer of funcparserlib expects to release 1.0.0 in the winter
> holidays so we may be able to fix this in the next week or so.

There is no ETA for hy yet, the devs are shaking up many things.

- Jelle




  reply	other threads:[~2021-12-22 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 11:24 bug#50356: python-hy / python-funcparserlib / tox config file Andreas Reuleaux
2021-09-17 12:32 ` Jelle Licht
2021-12-22 14:12   ` Vinicius Monego
2021-12-22 15:00     ` Jelle Licht [this message]
2021-12-22 16:53       ` Vinicius Monego
2021-12-29 23:46       ` Vinicius Monego

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=867dbwd6r9.fsf@fsfe.org \
    --to=jlicht@fsfe.org \
    --cc=50356@debbugs.gnu.org \
    --cc=monego@posteo.net \
    --cc=rx@a-rx.info \
    /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).