From: Vinicius Monego <monego@posteo.net>
To: Jelle Licht <jlicht@fsfe.org>, 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:53:05 +0000 [thread overview]
Message-ID: <c7b8871115bbb9b2b691d2cd950be4af6b034b6a.camel@posteo.net> (raw)
In-Reply-To: <867dbwd6r9.fsf@fsfe.org>
Em qua, 2021-12-22 às 16:00 +0100, Jelle Licht escreveu:
> 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?
>
Yes, again with 3 test failures, but the tests have different names
than that of 0.20.0.
[...]
>
next prev parent reply other threads:[~2021-12-22 16:54 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
2021-12-22 16:53 ` Vinicius Monego [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7b8871115bbb9b2b691d2cd950be4af6b034b6a.camel@posteo.net \
--to=monego@posteo.net \
--cc=50356@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.