Re: [python-team]: Time for Python 3.11.

What do you think about adding libxcrypt to python-3.11? The unmaintained but still influential python-passlib fails to detect support for some crypt() primitives, and I think we can fix this by building python-3.11 with libxcrypt support. We build Python 3.10 (as well as Python 2) with libxcrypt

Re: [python-team]: Time for Python 3.11.

Sharlatan Hellseher writes: > As Ricardo pushed python-3.11 and set it as default on python-team > branch it's triggered world rebuild. I started fixing some packages already by removing instances of the "U" file mode. You may find this document helpful in fixing problems: https://docs.pytho

Re: [python-team]: Time for Python 3.11.

Feel free to send patches. I have limited time to review large patch sets. I'm able to review single small patches or small patch series (1-3). all best, jgart

Re: python-team: New branch

On Sat, Dec 21, 2024 at 09:33:31PM +0100, Ricardo Wurmus wrote: > Ricardo Wurmus writes: > > > I've just rebased python-team on top of master, because Maxim just > > pushed some changes to python-tox etc to the master branch. > > Perhaps prematurely I rebased python-team on top of rust-team to b

Re: python-team: New branch

Hi, Ricardo and Maxim do you have any list of packages you are about to refresh/fix on python-team? I've finished with Astro update for this month and may provide my time for python-team. Thanks, Oleg

Re: python-team: New branch

Ricardo Wurmus writes: > I've just rebased python-team on top of master, because Maxim just > pushed some changes to python-tox etc to the master branch. Perhaps prematurely I rebased python-team on top of rust-team to benefit from upgrades needed for pydantic. When rust-team is rebased on top

Re: python-team: New branch

Hi Ricardo, Ricardo Wurmus writes: > Maxim Cournoyer writes: >> I have a Python mass update branch I've been developing, holding it back >> because I kept finding breakage (whether caused by my changes or >> already there). There's now 200 commits in it, including an update to >> virtualenv an

Re: python-team: New branch

Maxim Cournoyer writes: > I have a Python mass update branch I've been developing, holding it back > because I kept finding breakage (whether caused by my changes or > already there). There's now 200 commits in it, including an update to > virtualenv and typing extensions, along Python build syst

Re: python-team: New branch

Hi Ricardo, Ricardo Wurmus writes: > Hi Guix, > > I'm CC'ing the python-team. > > Since the merge of the python-team branch we've seen a bunch of > new build failures to popular packages. I've started work to repair > some of the damage. > > I think we should start a new python-team branch wher

Re: python-team: New branch

Sharlatan Hellseher writes: > I've pulled and initiated local rebuild for > >guix build -P 2 python-astropy > > I'll push any fixes if it failes. Thank you! I've just rebased python-team on top of master, because Maxim just pushed some changes to python-tox etc to the master branch. -- Ri

Re: Re: python-team: New branch

Hi, I've pulled and initiated local rebuild for guix build -P 2 python-astropy I'll push any fixes if it failes. -- Oleg signature.asc Description: PGP signature

Re: python-team: New branch

Ricardo Wurmus writes: > If there is more time we should also consider upgrading these packages: > > python-typing-extensions > python-virtualenv > python-platformdirs > python-colorama > python-chardet > > (I patched out version checks in python-tox to avoid upgrading, but I

Re: python-dbus-python changes triggered many rebuilds

Ian Eure writes: Would it make sense to sort package inputs when computing derivations to prevent this sort of unintentional change? The order matters, e.g. when we add a different gcc to shadow the existing gcc. -- Ricardo

Re: python-dbus-python changes triggered many rebuilds

Hi, I've canceled the pending builds. Sorry it was me, not expected that order of the same inputs would trigger the build. The reasoning was to refactor the indentation and higlight that python-meson-python has to be replaced by meson-python. Thanks, Oleg On Sat, 2 Nov 2024 at 00:20, Vagrant C

Re: python-dbus-python changes triggered many rebuilds

Would it make sense to sort package inputs when computing derivations to prevent this sort of unintentional change? I don't think the input order is important for the build, so this seems like it could be relatively simple to implement & avoid this recurring. On November 1, 2024 5:20:51 PM PDT

Re: python-duckdb stuck in its tests

Am Mon, Jul 08, 2024 at 11:41:12PM +0100 schrieb Sharlatan Hellseher: > I've pushed update togather with https://issues.guix.gnu.org/71480. It > fixed the build, check and sanity check phases in > ce98c3436c57e7b366a3ec06c47a7e8919c990fb. Excellent, thanks a lot! Andreas

Re: python-duckdb stuck in its tests

Hi, I've pushed update togather with https://issues.guix.gnu.org/71480. It fixed the build, check and sanity check phases in ce98c3436c57e7b366a3ec06c47a7e8919c990fb. Thanks, Oleg On Sun, 30 Jun 2024 at 11:02, Sharlatan Hellseher wrote: > > Hi Andreas, > > It looks like updating to 1.0.0 has n

Re: python-duckdb stuck in its tests

Hi Andreas, It looks like updating to 1.0.0 has not issue wit passing test on my local checkout after applying this patch --8<---cut here---start->8--- @@ -23334,20 +23334,24 @@ (define-public python-chevron (define-public python-duckdb (package (name

Re: [python-team] Weird python-notebook test failures

[resending as a wide reply, sorry] Felix Lechner writes: > Hi Ricardo, > > On Sat, Apr 06 2024, Ricardo Wurmus wrote: > >> Any ideas what might be going on here? > > Could it be "ModuleNotFoundError: No module named 'jupyter_server'"? I don't think so. There is no jupyter_server module in the

Re: [python-team] Weird python-notebook test failures

Hi Ricardo, On Sat, Apr 06 2024, Ricardo Wurmus wrote: > Any ideas what might be going on here? Could it be "ModuleNotFoundError: No module named 'jupyter_server'"? Kind regards Felix

Re: python importers as an alternative to propagated-inputs

Justin Veilleux writes: > Hi everyone. I was thinking about the propagated-inputs field in package > definitions. As I understand it, it is useful as a way to replace RPATHs > in packages that aren't compiled or don't support them. > > I was reading the documentation on > https://docs.python.or

Re: Python Team: Keeping Branch Up To Date Question

So, I should add a Python teams specific section to the texinfo docs?

Re: Python Team: Keeping Branch Up To Date Question

Hi jgart, "jgart" writes: > Thanks, I ended up doing what you suggested. > > Should we document this git branch policy for contributors with commit access > in the manual? > > I think we should state it explicitly so there is no confusion for new > contributors with commit access. If document

Re: Python Team: Keeping Branch Up To Date Question

Thanks, I ended up doing what you suggested. Should we document this git branch policy for contributors with commit access in the manual? I think we should state it explicitly so there is no confusion for new contributors with commit access. all best, jgart

Re: Python Team: Keeping Branch Up To Date Question

Hi, Lars-Dominik Braun writes: > Hi, > >> What is the git approach for keeping the Python branch up to date? 🦆 >> Should I be rebasing off of master or something else? > > yeah, that’s generally what I would do before working on it. Note that > you cannot force-push into Savannah. You have to re

Re: Python Team: Keeping Branch Up To Date Question

Hi, > What is the git approach for keeping the Python branch up to date? 🦆 > Should I be rebasing off of master or something else? yeah, that’s generally what I would do before working on it. Note that you cannot force-push into Savannah. You have to remove the remote branch and create it again.

Re: python-nbconvert build fails

Am Sun, Jul 23, 2023 at 08:23:36PM +0100 schrieb Christina O'Donnell: > Sorry, I've just seen this is a duplicate of > https://issues.guix.gnu.org/64729. > I should have checked there first! No problem, thanks for the report anyway! The package builds now, so a new "guix pull" should be enough.

Re: python-nbconvert build fails

Sorry, I've just seen this is a duplicate of https://issues.guix.gnu.org/64729. I should have checked there first! On 23/07/2023 20:15, Christina O'Donnell wrote: Hi Guix! This is my first time posting on a GNU mailing list so I'd

Re: Python feature branch

Hi all, On Mon, May 08, 2023 at 07:28 PM, Lars-Dominik Braun wrote: > Hi Andreas, > >> I wanted to set up automatic building on cuirass for the Python updates >> branch, but was not sure which one it is: >> $ git branch -a | grep python >> remotes/origin/python-updates >> remotes/origin/wip-p

Re: Python feature branch

Lars-Dominik Braun writes: > @Ricardo, Vivien: Can you confirm wip-python-graphviz and wip-python-mne > are stale/unused? Yes, I don’t use them and don’t even remember them. IIRC wip-python-graphviz has long been merged, so it’s fine to delete it. Thanks! -- Ricardo

Re: Python feature branch

Hi Andreas, > I wanted to set up automatic building on cuirass for the Python updates > branch, but was not sure which one it is: > $ git branch -a | grep python > remotes/origin/python-updates > remotes/origin/wip-python-graphviz > remotes/origin/wip-python-mne > remotes/origin/wip-python

Re: Python feature branch

Hello, I wanted to set up automatic building on cuirass for the Python updates branch, but was not sure which one it is: $ git branch -a | grep python remotes/origin/python-updates remotes/origin/wip-python-graphviz remotes/origin/wip-python-mne remotes/origin/wip-python-pep517 Some of th

Re: Python feature branch

Hi, I've fixed the build and updated chain of inputs for python-astropy, posting here for wider awareness. Thanks, Oleg

Re: python-ledgerblue as input for electrum? (was: Core-updates, the last metres)

Hi, On Sun, Apr 23, 2023 at 04:32 PM, Vagrant Cascadian wrote: > On 2023-04-23, Guillaume Le Vaillant wrote: >> Here are a few leaf packages that don't build because of some >> failing dependencies: >> - blender is blocked by opencolorio >> - electrum is blocked by python-ledgerblue > > Hrm thi

Re: python-pytest on core-updates (was: i686 core-updates failure.)

Am Sat, Apr 15, 2023 at 01:20:07PM +0200 schrieb Andreas Enge: > The recent master/staging merge apparently broke python-pytest even on > x86_64, see message below, which should be sorted out first. With pytest repaired, your patch builds numpy successfully on both x86 architectures. Pushed, thank

Re: python-pytest on core-updates

Am Sat, Apr 15, 2023 at 01:20:07PM +0200 schrieb Andreas Enge: > The recent master/staging merge apparently broke python-pytest even on > x86_64, see message below, which should be sorted out first. I tried to update to the more recent versions 7.2.2 and 7.3.1, but the recipe does not work out of

Re: python-pytest on core-updates (was: i686 core-updates failure.)

Am Fri, Apr 14, 2023 at 08:05:46PM + schrieb Kaelyn: > I just sent in https://issues.guix.gnu.org/62843 to disable the two tests for > i686 and armhf (disabling TestKind.test_all for armhf might not be needed, > but the Gentoo package definition suggests the huge array test will fail for > a

Re: Python

Am Thu, Mar 30, 2023 at 01:05:43PM +0200 schrieb Lars-Dominik Braun: > > its dependents. Without luck, now python-trio fails. > this one’s also fixed, see > cf26ee1f99f84f817f96269541073846d546026b gnu: python-trio: Run pytest on > tests directory only. Thanks for putting in all this energy! And

Re: Python

Hi again, > I just updated python-ipython to the first version that passes all tests > without any change, in the hope that this would have the least impact on > its dependents. Without luck, now python-trio fails. Updating this to the > latest version 0.22 does not help. I copy-paste the error me

Re: Python

Hello Lars, Am Thu, Mar 30, 2023 at 11:57:53AM +0200 schrieb Lars-Dominik Braun: > python-pyqt and python-pyqtwebengine should build on core-updates > now. I’ve tested qutebrowser, which works. splendid, thanks a lot for this major piece of work! > Other packages depending on python-pyqt fail du

Re: Python

Hello Andreas, > I looked at it and it seems that python-sip and python-pyqt-builder need a > version bump and we should maybe switch to pyproject-build-system. However > python-sip does not expose any switches to specify a different path for > .sip file includes. That requires custom patches for

Re: Python

Hi, > Well, there is pyqt as written elsewhere, but this is not only python. I looked at it and it seems that python-sip and python-pyqt-builder need a version bump and we should maybe switch to pyproject-build-system. However python-sip does not expose any switches to specify a different path fo

Re: Python

Am Sat, Mar 18, 2023 at 10:43:17AM +0100 schrieb Lars-Dominik Braun: > Anything else that needs work? Well, there is pyqt as written elsewhere, but this is not only python. I just updated python-ipython to the first version that passes all tests without any change, in the hope that this would hav

Re: Python

Am Sat, Mar 18, 2023 at 11:02:57AM +0100 schrieb Lars-Dominik Braun: > I just saw it was fixed on the develop branch already, but there’s no > new release: > https://github.com/kurtmckee/feedparser/commit/c55bd8ad37db89bd219783bc514d600c9523ed38 This dates from 2021, but strangely is not part of a

Re: Python

Hello Andreas, > excellent! It contradicts the feedparser author's statement that everything > works well, so if you have the courage, maybe you could report the issue > upstream. I just saw it was fixed on the develop branch already, but there’s no new release: https://github.com/kurtmckee/feedp

Re: Python

Hi again, > > > Right now I am left with a number of test failures that look real and > > > cannot > > > easily be solved by an upgrade (either because we are already on the > > > latest > > > version or because the tests still fail): python-sgmllib3k, > > > python-typeguard > > > and python-co

Re: Python

Hello Lars, Am Sat, Mar 18, 2023 at 09:59:37AM +0100 schrieb Lars-Dominik Braun: > I fixed both python-sgmllib3k and python-feedparser. Disabling tests > would not do much in this case, since the packages really *were* broken > by a Python upstream change. excellent! It contradicts the feedparser

Re: Python

Hello Andreas, > This one is used for python-feedparser, used for calibre and quodlibet. > The feedparser author is not enclined to work on it: >https://github.com/kurtmckee/feedparser/issues/328 > I would suggest to try compiling python-sgmllib3k (and potentially > python-feedparser) without

Re: Python

Hello, Am Sat, Feb 25, 2023 at 05:56:59PM +0100 schrieb Lars-Dominik Braun: > > Right now I am left with a number of test failures that look real and cannot > > easily be solved by an upgrade (either because we are already on the latest > > version or because the tests still fail): python-sgmllib3

Re: Python

Am Sat, Mar 11, 2023 at 12:20:25PM +0100 schrieb Andreas Enge: > There is a bug report for feedparser: >https://github.com/kurtmckee/feedparser/issues/328 > Unfortunately it was immediately closed with a link to an alternative > project by the feedparser author, but which has seen its latest re

Re: Python

Am Sat, Feb 25, 2023 at 07:00:30PM +0100 schrieb Andreas Enge: > > sgmllib3k looks pretty dead upstream. Perhaps it’s > > not even needed any more? Updates to Python packages (via `guix refresh`) > > do not update dependencies and thus the list of inputs/native-inputs > > are most likely outdated.

Re: Python

Am Mon, Feb 27, 2023 at 08:14:54PM +0100 schrieb Lars-Dominik Braun: > I don’t think we should follow PyPi’s names strictly. python-cheetah3 > makes much more sense than python-ct3. That’s what upstream-name is for. Okay, I am fine with doing nothing :) Andreas

Re: Python

Hi, > I updated it to its latest version under its current name python-cheetah, > but would suggest to rename it to python-ct3. What do you think? I don’t think we should follow PyPi’s names strictly. python-cheetah3 makes much more sense than python-ct3. That’s what upstream-name is for. Lars

Re: Python

Hi, > Do we have a list of packages in the python importer that can be removed > from inputs? Like already exists for hackage (and maybe others)? I’m not aware of any list like that and to compile it we’d probably have to build all python-* packages and check whether any of their installed modules

Re: Python

On Fri, Feb 24, 2023 at 07:08:44PM +0100, Lars-Dominik Braun wrote: > Hi Andreas, > > sorry, I can’t quite keep up with the Python issues on core-updates > right now :( > > > Yet another python failure: python-pathlib > this is a backport of Python’s built-in pathlib library. It should be > dropp

Re: Python

Am Sat, Feb 25, 2023 at 07:15:24PM +0100 schrieb Andreas Enge: > Actually, upstream has changed its pypi name! >https://pypi.org/project/CT3/ I updated it to its latest version under its current name python-cheetah, but would suggest to rename it to python-ct3. What do you think? Andreas

Re: Python

Am Sat, Feb 25, 2023 at 07:00:30PM +0100 schrieb Andreas Enge: > It is also a propagated input of python-feedparser And this fails its tests after disabling the tests of python-sgmllib3k, even after updating to its latest version 6.0.10, like below. Then why I was at it, I also disabled the tests

Re: Python

Am Sat, Feb 25, 2023 at 07:06:31PM +0100 schrieb Andreas Enge: > Python-cheetah is misnamed, it should be called python-cheetah3; the first > one is the python@2 version, both exist on pypi. Is it okay to rename it? > It looks like moderate work: > > $ guix refresh -l python-cheetah > Die folgende

Re: Python

Python-cheetah is misnamed, it should be called python-cheetah3; the first one is the python@2 version, both exist on pypi. Is it okay to rename it? It looks like moderate work: $ guix refresh -l python-cheetah Die folgenden 6 Pakete zu erstellen, würde zur Folge haben, dass 9 abhängige Pakete ne

Re: Python

Am Sat, Feb 25, 2023 at 05:56:59PM +0100 schrieb Lars-Dominik Braun: > Well, there are reasons no-one is updating the Python ecosystem > regularly… ;-) > I don’t know for sure why any of these packages’ tests fail. typeguard > looks like it expects specific strings from Python or one of its libra

Re: Python

Am Sun, Feb 19, 2023 at 09:27:23PM +0100 schrieb Andreas Enge: > Am Sun, Feb 19, 2023 at 04:50:37PM +0100 schrieb Lars-Dominik Braun: > > eolie upstream looks dead, same with jrnl. Removed. > I found python-miio, which depends on python-android-backup, which depends > on python-pycrypto. > The fi

Re: Python

Hi, > Right now I am left with a number of test failures that look real and cannot > easily be solved by an upgrade (either because we are already on the latest > version or because the tests still fail): python-sgmllib3k, python-typeguard > and python-coveralls. See messages below. I don’t know f

Re: Python

Am Sat, Feb 25, 2023 at 04:45:39PM +0100 schrieb Lars-Dominik Braun: > note that importlib-metadata is – again – part of the standard > library, as the table on [1] points out. So if we would ship Python 3.12, > we would not need it. Bumping it to version 5.2 seems like the correct > approach right

Re: Python

Hi Andreas, > This version requires python-importlib-metadata; not its latest version 6, > but something at least 5 and less than 6. We were still at 4.something. > So I have just updated it to 5.2.0, the latest version 5 from last December. > This gives me python-json-spec, so I am one step close

Re: Python

Hello Lars, Am Fri, Feb 24, 2023 at 07:08:44PM +0100 schrieb Lars-Dominik Braun: > sorry, I can’t quite keep up with the Python issues on core-updates > right now :( thanks for your reply, this is very helpful, as I am more than insecure when it comes to python packaging! > > Yet another python

Re: Python

Hi Andreas, sorry, I can’t quite keep up with the Python issues on core-updates right now :( > Yet another python failure: python-pathlib this is a backport of Python’s built-in pathlib library. It should be dropped as a dependency for all of these packages, since our Python is >= 3.4 – the versi

Re: Python

Am Fri, Feb 24, 2023 at 05:47:33PM +0100 schrieb Andreas Enge: > Yet another python failure: python-pathlib Maybe this is our fault; Debian has a pathlib2 package. Us too. So we should try to see whether we can replace the dependency python-pathlib by python-pathlib2. Work for another day. Andre

Re: Python

Yet another python failure: python-pathlib import pathlib File "/tmp/guix-build-python-pathlib-1.0.1.drv-0/pathlib-1.0.1/pathlib.py", line 10, in from collections import Sequence ImportError: cannot import name 'Sequence' from 'collections' (/gnu/store/blals34ar25fiifvm17m2b504waxzys0-pyt

Re: Python

Another very problematic python package: python-sgmllib3k It fails its tests in core-updates. Unmaintained since 2010, the author states that they do not wish to maintain it. Some dependencies: Building the following 6 packages would ensure 8 dependent packages are rebuilt: emacs-calibredb@2

Re: Python

In my goal of building calibre on core-updates, I encounter many build failures. The Python package graph seems to be extremely entangled, with dependencies on specific input package and even Python versions. The only approach I could imagine is updating to newer versions, and this solved some of

Re: Python (was: Merging core-updates?)

Hello, Am Sun, Feb 19, 2023 at 11:24:44PM +0100 schrieb Andreas Enge: > python-graphviz does not pass its tests any more in core-updates, and > I can trace it back to your commit 3d388fe3d0475f2e991ae061cc1364529a97af42. > Adding python-mock back to native-inputs fixes it. I opted for this fix an

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 12:30:42PM +0100 schrieb Andreas Enge: > And another one: python-ecdsa This just built. Strange, but I will not complain! Andreas

Re: Python

Am Sun, Feb 19, 2023 at 09:31:44PM +0100 schrieb Andreas Enge: > And yet another one: python-testtool > FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error > FAIL: > testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error This is reported upstream

Re: Python

Am Sun, Feb 19, 2023 at 03:10:03PM + schrieb Attila Lendvai: > weirdly enough, upstream uses one git repo for multiple projects, and uses > prefixed tag names for them. > FYI, there's this long-pending patchset to update the trezor-agent (something > i can test myself): > https://issues.guix.

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 10:59:35PM + schrieb Kaelyn: > It was mentioned recently that python-pycryptodome is / should be a drop-in > replacement for python-pycrypto (it is also says that in the package > description); Apparently it is not, as Lars wrote. And in any case, it does require some

Re: Python (was: Merging core-updates?)

--- Original Message --- On Sunday, February 19th, 2023 at 10:08 PM, Andreas Enge wrote: > > There is poezio, which has a new release (0.14), with a license change to > gpl3+. I updated python-slixmpp, a dependency of poezio, but this is not > enough: The newest poezio still depends on

Re: Python (was: Merging core-updates?)

Hello Ricardo, python-graphviz does not pass its tests any more in core-updates, and I can trace it back to your commit 3d388fe3d0475f2e991ae061cc1364529a97af42. Adding python-mock back to native-inputs fixes it. Or maybe python-pytest-mock should have python-mock as propagated input? It calls it

Re: Python (was: Merging core-updates?)

There is poezio, which has a new release (0.14), with a license change to gpl3+. I updated python-slixmpp, a dependency of poezio, but this is not enough: The newest poezio still depends on python-potr, which in turn depends on python-pycrypto. Andreas

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 04:50:37PM +0100 schrieb Lars-Dominik Braun: > The rest seems to be alive > without any references to python-pycrypto. So these should be upgradable > and then we can drop python-pycrypto. I more or less got rid of one of them: python-ledgerblue. I have updated it from 0.1.

Re: Python

And yet another one: python-testtool Tests running... == FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error -- Traceback (most recent cal

Re: Python

Am Sun, Feb 19, 2023 at 04:50:37PM +0100 schrieb Lars-Dominik Braun: > eolie upstream looks dead, same with jrnl. How do we drop them from the distribution? Do we need to prepare a NEWS item? > The rest seems to be alive > without any references to python-pycrypto. So these should be upgradable >

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 12:57:07PM +0100 schrieb Andreas Enge: > > which seems to be the only change in attrdict3, see > > https://github.com/pirofti/AttrDict3/commit/f6678b627b469c9aeddca2a9e4ba4e1ee9e3ccbb > Great, I will replace the package then. Done. Interestingly enough, there was only one

Re: Python (was: Merging core-updates?)

Hi, > Except that we have to decide what to do about its dependents... upgrade or drop if not possible. pycryptodome does not provide an entirely compatible interface (see https://www.pycryptodome.org/src/vs_pycrypto), so we cannot simply switch existing packages from pycrypto to pycryptdome witho

Re: Python (was: Merging core-updates?)

> but it is somehow in the same git repository as trezor-agent, > and I do not totally understand how these are related. Taking > back my rant and acknowledging my ignorance. weirdly enough, upstream uses one git repo for multiple projects, and uses prefixed tag names for them. FYI, there's this

Re: Python (was: Merging core-updates?)

Hello Lars, thanks for having a look! Am Sun, Feb 19, 2023 at 12:47:46PM +0100 schrieb Lars-Dominik Braun: > > command "python" "-m" "compileall" "--invalidation-mode=unchecked-hash" > > "/gnu/store/5i3yqwaqd8mayl2vr9lmrihxwv8203b1-python-pycrypto-2.6.1" failed > > with status 1 > this particul

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 12:02:15PM +0100 schrieb Andreas Enge: >Then we have: > Building the following 6 packages would ensure 9 dependent packages are > rebuilt: python-miio@0.5.11 ledger-agent@0.9.0 electrum@4.3.2 eolie@0.9.101 > jrnl@1.9.7 poezio@0.13.2 Concerning poezio, it depends

Re: Python (was: Merging core-updates?)

Hi Andreas, > *** File > "/gnu/store/5i3yqwaqd8mayl2vr9lmrihxwv8203b1-python-pycrypto-2.6.1/lib/python3.10/site-packages/Crypto/Util/number.py", > line 139 > value |= 2L ** (N-1)# Ensure high bit is set > ^ > SyntaxError: invalid decimal literal > error: in pha

Re: Python (was: Merging core-updates?)

And another one: python-ecdsa I tried to update it from 0.17.0 to 0.18.0, but it still fails its tests with this message: src/ecdsa/test_jacobi.py:393: TypeError === warnings summary === src/ecdsa/test_der.py::TestEncodeBitstring::test_implic

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 12:15:59PM +0100 schrieb Andreas Enge: > I am looking at these packages. One of them, ledger-agent, dates from 2017 > and has seen 25 releases in the meantime. Well, maybe, maybe not. The version in Pypi has not changed, but it is somehow in the same git repository as trezo

Re: Python (was: Merging core-updates?)

Am Sun, Feb 19, 2023 at 12:02:15PM +0100 schrieb Andreas Enge: > PPS: On the first issue, the homepage says: >PyCrypto 2.x is unmaintained, obsolete, and contains security > vulnerabilities. > Building the following 6 packages would ensure 9 dependent packages are > rebuilt: python-miio

Re: Python Packaging Policy

On Thu, Dec 08, 2022 at 11:48:42AM +0100, zimoun wrote: > Hi, > > On Wed, 07 Dec 2022 at 17:22, jgart wrote: > > > What is our policy then for updating Python packages in our Python > > library collection? > > The policy is to not break the other packages; guix refresh -l python-. > > > > How

Re: Python Packaging Policy

Hi, On Wed, 07 Dec 2022 at 17:22, jgart wrote: > What is our policy then for updating Python packages in our Python > library collection? The policy is to not break the other packages; guix refresh -l python-. > How are we assuring that all Python libraries are working well together? How? W

Re: python-pytest in references graph

Hi Bengt, Berlin is currently in a degraded state (probably a Shepherd bug). The main Web site works, although it's probably not being updated, and last I checked substitutes did to, but issues. is down and I don't think Cuirass is building new substitutes. We can't remotely reset the machine

Re: python-pytest in references graph

On +2022-07-25 08:23:57 +0200, Lars-Dominik Braun wrote: > Hi, > > > It should, but sometimes there are bugs in the package definition or > > build system, in this case causing python-rdflib to refer to the > > native-input python-pytest.  Likely it's the 'add-install-to-path' phase > > adding

Re: python-pytest in references graph

Hi, > It should, but sometimes there are bugs in the package definition or > build system, in this case causing python-rdflib to refer to the > native-input python-pytest.  Likely it's the 'add-install-to-path' phase > adding too much, a known issue, which could be solved by separating > input

Re: python-pytest in references graph

On Sun, 2022-07-24 at 23:01 +0200, Maxime Devos wrote: > > On 24-07-2022 22:25, Roel Janssen wrote: > > I'm trying to understand the output of: > > $ guix graph --type=references python-rdflib | dot -Tsvg -o rdflib.svg > > > > Particularly, I'm looking at why python-pytest has an input arrow from

Re: python-pytest in references graph

On 24-07-2022 22:25, Roel Janssen wrote: I'm trying to understand the output of: $ guix graph --type=references python-rdflib | dot -Tsvg -o rdflib.svg Particularly, I'm looking at why python-pytest has an input arrow from python-rdflib, while it's "only" a native-input? I thought the "refere

Re: python-libcst upgrade and python-flake8

Hi jgart, > validating 'flake8' > /gnu/store/zaw5z708sldm6v3qxjczcia7gl65dw5x-python-flake8-3.9.2/lib/python3.9/site-packages > ...checking requirements: ERROR: flake8==3.9.2 > ContextualVersionConflict(pyflakes 2.4.0 > (/gnu/store/mxkp1zl64cd3i247shp7njkxad8v13x9-python-pyflakes-2.4.0/lib/pyth

Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]

Hello, Efraim Flashner skribis: > On Sun, May 15, 2022 at 11:22:05PM +0200, Ludovic Courtès wrote: [...] >> Yes, so what do you mean? Should we keep the old 3.3.1 for use on >> non-x86_64 platforms? Would that even work? > > I'll add 3.4.8 for non-x86_64 platforms and see if I can do somethi

Re: python-cryptography and rust [was: Re: ‘staging’ branch is open!]

On Sun, May 15, 2022 at 11:22:05PM +0200, Ludovic Courtès wrote: > Hi Efraim, > > (+Cc: Marius.) > > Efraim Flashner skribis: > > > python-cryptography now depends on rust. We're going to need 3.4.8 from > > the 3.4 series for the other architectures. Currently > > python-cryptography@36.0.1 is

  1   2   3   4   >