[python-team] Error in the build-system with executable files

path #o755) - ;; PEP 427 recommends that installers rewrite - ;; this odd shebang. - (substitute* dest-path - (("#!python") -

Re: Jumping the queue: merge r-team before python-team?

Hello all, Am Sun, Apr 13, 2025 at 02:56:28PM +0200 schrieb Andreas Enge: > I have rebased the r-team branch on master without any problems and > pushed. So if you think r-team is ready now, please feel free to push > it to master. Ricardo has just pushed the branch to master, thanks to all for t

Re: Jumping the queue: merge r-team before python-team?

n them, it shows a 504 error now, but only very few failed builds yesterday. News of python-team is that they might need an additional week, qt-team should start to build soon on QA. I have rebased the r-team branch on master without any problems and pushed. So if you think r-team is ready now,

Re: Jumping the queue: merge r-team before python-team?

Andreas Enge skribis: > How about profiting from our duplicate build farms by building in > parallel r-team on berlin/CI and qt-team and tex-team on bordeaux/QA? I believe ‘r-team’ is already being built: https://ci.guix.gnu.org/jobset/r-team Ludo’.

Re: Jumping the queue: merge r-team before python-team?

to Chris's work described in https://issues.guix.gnu.org/75894 we expect the node team branch to be merged in the next few days, and hopefully the python-team branch is also close to completion. In any case, QA would pick up the next branch in line. How about profiting from our duplicate build

Re: Jumping the queue: merge r-team before python-team?

Hi Andreas, On Fri, Apr 11 2025, Andreas Enge wrote: > Well, why should r-team go before qt-team or tex-team? > (I have no particular opinion and am fine with any decision on that > matter, but one should search agreement by qt-team and tex-team Some "one" has to do it. Why not you? Kind regar

Re: Jumping the queue: merge r-team before python-team?

Hey, Greg Hogan skribis: > I'd rather have some team make progress than no one, and the only way > to dig ourselves out of this hole is to be more assertive as Ricardo > has been here. Let everyone else follow his lead soon after. Yes. I think it’s good that qa.guix.gnu.org and the correspondi

Re: Jumping the queue: merge r-team before python-team?

Ludovic Courtès writes: > Christopher Baines skribis: > >>> But we also need more flexibility, in particular the ability to say >>> “this branch is ready so it should be merged now”. Could we provide a >>> way to change the order of branches shown by qa.guix.gnu.org? >> >> The current mechanism

Re: Jumping the queue: merge r-team before python-team?

up. > Did I get that right? Yes, that is right. Actually we normally build the top two branches, so it could also remain behind python-team. > Let’s do that, then! Well, why should r-team go before qt-team or tex-team? (I have no particular opinion and am fine with any decision on that m

Re: Jumping the queue: merge r-team before python-team?

Christopher Baines skribis: >> But we also need more flexibility, in particular the ability to say >> “this branch is ready so it should be merged now”. Could we provide a >> way to change the order of branches shown by qa.guix.gnu.org? > > The current mechanism to do this is mentioned on [1], b

Re: Jumping the queue: merge r-team before python-team?

"ready" includes "being built on QA"... > Could we provide a > way to change the order of branches shown by qa.guix.gnu.org? We already did that by closing the core-packages-team and (temporarily) python-team branches, and letting elogind-updates and node-team go to the fron

Re: Jumping the queue: merge r-team before python-team?

Ludovic Courtès writes: > Greg Hogan skribis: > >> I'd rather have some team make progress than no one, and the only way >> to dig ourselves out of this hole is to be more assertive as Ricardo >> has been here. Let everyone else follow his lead soon after. > > Yes. I think it’s good that qa.gui

Re: Jumping the queue: merge r-team before python-team?

Am Fri, Apr 11, 2025 at 06:35:35AM -0700 schrieb Felix Lechner: > Your branch should be merged now (and before you update R) after our new > branch merge coordinator, Andreas Enge, signs off. No, no, I have never signed on that role. In particular, I am here only to push my own branches. :) So fa

Re: Jumping the queue: merge r-team before python-team?

Hi Ricardo, On Fri, Apr 11 2025, Ricardo Wurmus wrote: > There has now been a new R release while the branch has been waiting Upstream will always do as they please. To us, it's more important what's in Guix. Your branch should be merged now (and before you update R) after our new branch merge

Re: Jumping the queue: merge r-team before python-team?

Hi Andreas, On Tue, Apr 01 2025, Andreas Enge wrote: > Probably we also need some human scheduler. In the past it has happened > that branches have clogged the queue although for a week or two nobody > was available to work on it. Having a person following the branches and > interacting with the

Re: Jumping the queue: merge r-team before python-team?

Hello, Am Tue, Apr 01, 2025 at 09:39:51AM -0400 schrieb Greg Hogan: > QA shows no status ("Yet to process target revision") for python-team > and core-packages-team (resurrected and now again the head of the > queue). I have just closed the core-packages-team issue, as it tur

Jumping the queue: merge r-team before python-team?

Hi Guix, the r-team branch has been ready for weeks. It has only accumulated more changes (like the upgrade of R itself) as it has been sitting in the queue. What do you think about letting this branch jump the queue ahead of python-team? -- Ricardo

Re: Numerical problem (compiling python-numba package)

Hi Emmanuel, On Wed, 12 Feb 2025 at 09:42, Emmanuel Medernach wrote: > AssertionError: when comparing [0.60858395 0.54922627 0.57440088] and > [0.60858395 0.54922627 0.57440088]: 0.549226270051226 != 0.5492262700512262 > > More generally this asks the question about reproducibility of numerica

Re: Packaging the "next" Python

27;s a perfectly situation > > for inheritance. There is nothing wrong with use of inheritance for closely > > related package variants, such as python-3.12 and python-3.13. Only one of > > these versions will eventually remain, so one replaces the other in the long > > run.

Re: Packaging the "next" Python

Hi Tanguy, I tried this (define-public python-3.13 (package (inherit python-3.12) (version "3.13.2") (source (origin (inherit (package-source python-3.12)) (sha256 (base32 "0mpbb6hkzdphyin861ywqnxibh5i4gjl5vvxdyralz6ngk2vr16r"))

Re: Packaging the "next" Python

of inheritance for closely > related package variants, such as python-3.12 and python-3.13. Only one of > these versions will eventually remain, so one replaces the other in the long > run. I would not say "pressured", but I was a bit "disappointed" for I thou

Re: Packaging the "next" Python

nt after reading the messages here, I think it's a perfectly situation for inheritance. There is nothing wrong with use of inheritance for closely related package variants, such as python-3.12 and python-3.13. Only one of these versions will eventually remain, so one replaces the other in the

Re: Packaging the "next" Python

Hi Ricardo, On Thu Feb 27, 2025 at 3:05 PM CET, Ricardo Wurmus wrote: > Hi Tanguy, > >> ```scheme >> (define-public python-3.13 >> (package >> (inherit python-3.12) >> (version "3.13.2") >>

Re: Packaging the "next" Python

Hi Felix, On Thu Feb 27, 2025 at 3:14 PM CET, Felix Lechner wrote: > On Thu, Feb 27 2025, Leo Famulari wrote: > >> I always recommend against using inheritance > > Yes, it's like a disease! Please make the use of inheritance illegal in > package declarations except in approved cases. > > In all

Re: Packaging the "next" Python

lines of `(arguments >> …)` to >> make it work, even if I didn’t change a single line of it!? That sounds >> sub-optimal to me. Oh, and those exact same lines seem to be coming >> from 3.11!? > > General advice, not specific to Python: I always recommend against using &

Re: Packaging the "next" Python

Hi Leo, On Thu, Feb 27 2025, Leo Famulari wrote: > I always recommend against using inheritance Yes, it's like a disease! Please make the use of inheritance illegal in package declarations except in approved cases. In all circumstances, however, later package versions should never inherit from

Re: Packaging the "next" Python

Hi Tanguy, ```scheme (define-public python-3.13 (package (inherit python-3.12) (version "3.13.2") (source (origin (sha256 (base32 "0mpbb6hkzdphyin861ywqnxibh5i4gjl5vvxdyralz6ngk2vr16r")) (patches (search-patches "pyt

Re: Packaging the "next" Python

ne of it!? That sounds > sub-optimal to me. Oh, and those exact same lines seem to be coming > from 3.11!? General advice, not specific to Python: I always recommend against using inheritance, except in the very simplest cases. It quickly becomes very hard to understand and change, as it i

Packaging the "next" Python

Hi Python Team, hi Guix, I’ve started working on packaging the "next" Python. I realize that it might not make sense, for Guix and the Python Team, to work on this, and that it might have been better to help on getting the branch merged, but my professional use case for Guix is "

Questions about a duplicate package and naming of go/python/etc packages.

Hi, In January 2023 I added the docker-registry package while the go-github-com-docker-distribution package was there since 2018. This is most likely due to the way I named my package: I followed the other distributions (here Trisquel and Parabola) package name. While the way to go is to merge a

Re: Numerical problem (compiling python-numba package)

Hello, Sharlatan Hellseher skribis: > We may limit the test suite to bare minimum For the record, I reported the issue at . This appears to be an upstream problem with one specific test: https://github.com/numba/numba/issues/8282 Ludo’.

Re: Re: Numerical problem (compiling python-numba package)

We may limit the test suite to bare minimum Nix did it refering the same reason https://github.com/NixOS/nixpkgs/blob/nixos-24.11/pkgs/development/python-modules/numba/default.nix#L129 Oleg

Re: Numerical problem (compiling python-numba package)

Hi Emmanuel, > I don't know if guix-devel is appropriate to report issue with a > package. It's appropriate. > I have a problem installing the package python-numba version: 0.61.0, I > cannot compile it on my machine (it > compiles on others). While I cannot reproduc

Numerical problem (compiling python-numba package)

Hello I don't know if guix-devel is appropriate to report issue with a package. I have a problem installing the package python-numba version: 0.61.0, I cannot compile it on my machine (it compiles on others). Many tests are failing because of rounding errors su

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

Re: Guix's python has pip's user dir in its loadpath

e...@beaver-labs.com writes: > Dear Guix devs, > > While working around this bug: > > https://issues.guix.gnu.org/63912 > > I found that guix's Python will load anything in > .local/lib/python3.10/site-packages/ over any installed package in the > current profile.

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 fixi

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

[python-team]: Time for Python 3.11.

Hi Guix and Python team (CCed)! As Ricardo pushed python-3.11 and set it as default on python-team branch it's triggered world rebuild. My plan is to fix all failed packages required for NumPy and prepare v2, keeping v1 for later. Let's spread the efforts and coordinate

Re: Last minute python-team fixes: help needed!

Ricardo Wurmus writes: > Hi, > > I've spent the last weeks whipping the python-team branch into shape, > but I'm running out of steam. There are still a number of failures, and > I'm about to lose motivation to continue fixing the remaining build > failures. Th

Last minute python-team fixes: help needed!

Hi, I've spent the last weeks whipping the python-team branch into shape, but I'm running out of steam. There are still a number of failures, and I'm about to lose motivation to continue fixing the remaining build failures. Here are some of the failures that may be of inter

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 pytho

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 reb

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, inclu

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 extensio

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

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 pytho

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-to

python-team: New branch

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 where we build out important upgr

Re: bug#74715: Request for merging "python-team" branch

Hi, > Would it be helpful to open a bug about this? there is https://issues.guix.gnu.org/69997, which includes patches to add initial pyproject.toml support to `guix import pypi`. Lars

Re: bug#74715: Request for merging "python-team" branch

On Sun, Dec 15, 2024 at 10:29:03AM +, Sharlatan Hellseher wrote: > Hi, > > Maybe we may put some news about changes in pyproject build system? I think that's a great idea.

Re: bug#74715: Request for merging "python-team" branch

>dim. 15 déc. 2024 at 17:53, "Ian Eure" wrote: > Would it be helpful to open a bug about this? I confirm, this line (inputs (list python-setuptools python-wheel)) fixes the issue for me. However, ‘guix lint’ complaints about python-setuptools not necessary. -- Cayetano

Re: bug#74715: Request for merging "python-team" branch

Hi Lars-Dominik, On Sun, Dec 15, 2024, at 6:28 AM, Lars-Dominik Braun wrote: > Hi Ian, > >> Since this merge landed, the builds for several Python packages in my >> personal channel broke. Any package using pyproject-build-system for a >> Python project using setupto

Re: bug#74715: Request for merging "python-team" branch

Hi, Maybe we may put some news about changes in pyproject build system? Thanks Oleg

Re: bug#74715: Request for merging "python-team" branch

Hi Ian, > Since this merge landed, the builds for several Python packages in my > personal channel broke. Any package using pyproject-build-system for a > Python project using setuptools seems to be affected. as Sharlatan Hellseher wrote in https://issues.guix.gnu.org/issue/74715#4,

Re: bug#74715: Request for merging "python-team" branch

Hi Ian, On Saturday, December 14th, 2024 at 5:00 PM, Ian Eure wrote: > Hi all, > > Since this merge landed, the builds for several Python packages in my > personal channel broke.  Any package using pyproject-build-system for a > Python project using setuptools seems to be

Re: bug#74715: Request for merging "python-team" branch

Hi all, Since this merge landed, the builds for several Python packages in my personal channel broke. Any package using pyproject-build-system for a Python project using setuptools seems to be affected. This python-manhole package[1] is an example. It's about as simple as they ca

Re: bug#74715: Request for merging "python-team" branch

Hey there, https://qa.guix.gnu.org/ says it’s your turn to merge! :-) Ludo’.

Request for merging "python-team" branch

CC Python team for wider spread. signature.asc Description: PGP signature

Re: Status of python-team 2024-11-21

I can probably help this week-end with some focussed patches. Just to be sure about what the task is, it will be about fixing new python failures from the lastest eval at https://ci.guix.gnu.org/jobset/python-team, right ? PS: I don't have commit rights and won't ask them in the

Re: Status of python-team 2024-11-21

Andreas Enge writes: > My interest in the python branch is that I would like to install qmk, which > fails to build on master (due to python-uvicorn). I've fixed python-unicorn on master yesterday. -- Ricardo

Re: Status of python-team 2024-11-21

My interest in the python branch is that I would like to install qmk, which fails to build on master (due to python-uvicorn). On the new branch, an error appears much earlier, unfortunately, in /var/log/guix/drvs/vl/17hyiw24yvphw3xkp3m3dq066wdh5i-python-jupyter-core-5.7.2.drv.gz: FAILED tests

Re: Status of python-team 2024-11-21

Hello, after the qt-team merge, I have rebased and pushed the python-team branch on master. There was an easy to solve merge conflict in python-sip. Andreas

Re: Status of python-team 2024-11-21

Am Fri, Nov 22, 2024 at 10:39:55AM +0100 schrieb Nicolas Goaziou: > I don't know how texlive-hyphen-complete relates to cmake either. > texlive-hyphen-complete depends on Ruby. It is now available from this branch at CI, so it was indeed probably just a transient error for the person building loca

Re: Status of python-team 2024-11-21

Hello, Andreas Enge writes: > Am Thu, Nov 21, 2024 at 12:03:26PM + schrieb Sharlatan Hellseher: >> I've rebased and pushed all of my changes updating python-numpy, >> python-mypy and python-pandas with fixture of some packages linked for >> python-pandas. >>

Re: Status of python-team 2024-11-21

Am Thu, Nov 21, 2024 at 12:03:26PM + schrieb Sharlatan Hellseher: > I've rebased and pushed all of my changes updating python-numpy, > python-mypy and python-pandas with fixture of some packages linked for > python-pandas. > I might need some hands of help to check the ch

Status of python-team 2024-11-21

Hi Guix! I've rebased and pushed all of my changes updating python-numpy, python-mypy and python-pandas with fixture of some packages linked for python-pandas. I might need some hands of help to check the changes. Particular texlive-hyphen-complete is failing which linked to cmake (not sur

Re: Status of python-team branch

Hi Oleg, hi Python team, Quoting Sharlatan Hellseher (2024-11-05 14:47:56) > CC python-team > > Let's prepare the branch to be merged? Thanks for working on this. I do realize that, since I added myself to the team, I haven’t been really helpful. Sorry for that! 😞 I’ve been sp

Re: Status of python-team branch

Hi, CC python-team Let's prepare the branch to be merged? I took a flag to fix build issues on python-team after introducing adjustment to pyproject-build-system requiring python-setuptools and python-wheel somtimes to be availalbe in inputs. I try to minimise the amount of changes and

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, Va

Re: python-dbus-python changes triggered many rebuilds

:20:51 PM PDT, Vagrant Cascadian wrote: >A large rebuild was triggered by: > >commit a9abf9a7b30f6801e122cae759df87b44c458773 >Author: Sharlatan Hellseher >Date: Fri Nov 1 21:10:04 2024 + > >gnu: python-dbus-python: Fix indentation. > >* gnu/packages/pyth

python-dbus-python changes triggered many rebuilds

A large rebuild was triggered by: commit a9abf9a7b30f6801e122cae759df87b44c458773 Author: Sharlatan Hellseher Date: Fri Nov 1 21:10:04 2024 + gnu: python-dbus-python: Fix indentation. * gnu/packages/python-xyz.scm (python-dbus-python): Fix indentation, adjust order of fields

Re: Status of python-team branch

Hi, I got 31 from the 'start' of the branch applied: https://issues.guix.gnu.org/71408#13 There are notes on the ones I couldn't get working, and the python-project build system ones that Lars was going to cherry-pick separately. I've rebuild about 100+ dependent p

Re: Status of python-team branch

> > Same for me, starting resolving rebase conflict. > Hi Guixers, I would recommend cherry picking logical commits into new branches that can be quickly reviewed and merged by Guix volunteers. Steve made a list here of some logical commits that can go into new branches: https://issues.guix.g

Re: Status of python-team branch

yself to that > > - rebase on current master > > - resolve conflicts > > - apply pending patches from issues > > - push for testing > > - merge to master > > > > Is anyone interested in rebasing the branch? > > Are you still looking at rebasing python-

Re: Status of python-team branch

Sharlatan Hellseher writes: > Hi, > > I may volunteer myself to that > - rebase on current master > - resolve conflicts > - apply pending patches from issues > - push for testing > - merge to master > > Is anyone interested in rebasing the branch? Are you still l

Re: Status of python-team branch

Thanks! On Tue, 24 Sept 2024, 13:03 Sharlatan Hellseher, wrote: > > Hi necto, > > Please take a look at current merge status of the branch, it may be > delayed. > > https://issues.guix.gnu.org/71408 > > -- > Oleg >

Re: Status of python-team branch

Hi necto, Please take a look at current merge status of the branch, it may be delayed. https://issues.guix.gnu.org/71408 -- Oleg signature.asc Description: PGP signature

Re: Status of python-team branch

the future, I think we should have smaller topic branches. For example, we could request to update particular python packages with large rebuilds on a dedicated branch such as python-team-python-sphinx, one request at a time. I think that breaking up the team branch merge request into smaller

Re: Status of python-team branch

Hi, I may volunteer myself to that - rebase on current master - resolve conflicts - apply pending patches from issues - push for testing - merge to master Is anyone interested in rebasing the branch? > Oleg >

Re: Status of python-team branch

Lars-Dominik Braun writes: > Hi, > >> I'd like to check who is working on python-team branch to prepare it for >> the merge? > > I don’t think anyone is actively working on it right now. #71408 is > the place where any updates should be if there were any

Re: Status of python-team branch

Hi, > I'd like to check who is working on python-team branch to prepare it for > the merge? I don’t think anyone is actively working on it right now. #71408 is the place where any updates should be if there were any. CC’ing a few people who have contributed to the branch or state

Status of python-team branch

Hi Guix! I'd like to check who is working on python-team branch to prepare it for the merge? Especially I'd need to test a fresh version of python-attrs which involves rebuild of 1000+ packages: --8<---cut here---start->8--- > ./pre-in

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

ting 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 >

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

python-duckdb stuck in its tests

Hello the Python team, python-duckdb sticks out on the build farm, since it apparently gets blocked in its tests after spending quite some CPU time for building, and finally it times out after a day. It seems to happen consistently over several evaluations. The last lines are: tests/fast

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

[python-team] Weird python-notebook test failures

Hi Guix, on the python-team branch I'm slowly fixing build errors, but I can't figure out what's wrong with python-notebook: https://ci.guix.gnu.org/build/3872654/details Nothing big changed that would explain the build failure. It looks like the notebook server doesn'

Re: 07/07: gnu: Add python-docspec.

to be a >> Pytest test suite: >> https://github.com/NiklasRosenstein/python-docspec/tree/develop/docspec/test >> >> Fetching from git and adding pytest no native-inputs may be enough to >> have it run. >> >> Something to keep in mind for future submissions! &g

Re: 07/07: gnu: Add python-docspec.

Hi Maxim, > I'm not in the Python team, but I thought I'd give some feedback on > recent Python packages added. > > guix-comm...@gnu.org writes: > >> gnu: Add python-docspec. >> >> * gnu/packages/python-xyz.scm (python-docsp

Re: 07/07: gnu: Add python-docspec.

Hi, I'm not in the Python team, but I thought I'd give some feedback on recent Python packages added. guix-comm...@gnu.org writes: > gnu: Add python-docspec. > > * gnu/packages/python-xyz.scm (python-docspec): New variable. >

Re: python importers as an alternative to propagated-inputs

ric solution, but it provided the minimal reasons to replace our use of PYTHONPATH with GUIX_PYTHONPATH, which we enable with a generated “sitecustomize.py” file — see (gnu packages python) for details. It would be great if we could do without GUIX_PYTHONPATH, which forces us to harmonize *all* Python

python importers as an alternative to propagated-inputs

...,pandas=/gnu/store/... This would make propagated-inputs for python libraries and programs unnecessary. Does someone know if this has been tried before? What potential problems would I encounter if I tried to implement this? Cheers.

Re: Question on python-pydantic update, rust and maturin build tool

Sharlatan Hellseher writes: > It might be addressed to rust/python teams. > https://github.com/pydantic/pydantic-core > > During update of some packages from (gnu packages astronomy) I've faced with > requirement for the fresh version of pydantic which > depends on p

Re: Question on python-pydantic update, rust and maturin build tool

Hi Efraim, I was about to update python-hvpy to v1.1.0 which requires pydantic>=2.0.0 https://github.com/Helioviewer-Project/python-api/blob/v1.1.0/setup.cfg#L37 Pydantic 2+ (the latest is v2.5.3 2023-12-22) depends on pydantic-core (the latest is v2.14.6 2023-12-21) which is built w

  1   2   3   4   5   6   7   8   9   10   >