Skip to content

Conversation

@maxhbr
Copy link
Contributor

@maxhbr maxhbr commented Feb 4, 2025

might be helpful / is WIP.

@otavio
Copy link
Contributor

otavio commented Feb 4, 2025

I suggest we create a Python packages folder where we add one package file for each one and handle that automatically.

One way we can do that is using and use that to add that to the Python namespace automatically. Take a look at how we do it back in our project:

...
      perSystem = { self', config, system, pkgs, ... }: {
        _module.args.pkgs = import inputs.nixpkgs {
          inherit system;
          overlays = [
            (_: prev: {
              python3 = prev.python3.override {
                packageOverrides = _: _:
                  inputs.by-name.lib.trivial prev.python3Packages.callPackage ./pkgs/python-by-name;
              };
            })
          ];
        };
...

It would allow you to have one folder for each package and make it easy to go upstream in the future.

@dvalnn
Copy link

dvalnn commented Mar 26, 2025

your fork @maxhbr works for me on nixpkgs stable (nixos-24.11) and with zephyr 4.1.0.

The only problem I have noticed so far is an evaluation warning for invalid ruff constraints, but the dev shell seems to be working fine.

@leonardp
Copy link

leonardp commented Mar 28, 2025

works for me aswell thanks @maxhbr

it tested it for zephyr-4.1.0 and nixpkgs-unstable:
the gcovr package will move to top level in nixpkgs, with these changes it worked:
master...leonardp:zephyr-nix:python-workaround#diff-121723bd099d78392acde83993a7ab1c66aaafabe9308dabec77d9cde161f858

@adisbladis adisbladis force-pushed the master branch 2 times, most recently from 1145e84 to fb64a83 Compare July 31, 2025 03:28
@adisbladis adisbladis changed the title FYI: changes I did on my way to get it running for 4.0.0 Support Zephyr 4.x Jul 31, 2025
The latter currently fails because of ceph/arrow-cpp.
@adisbladis adisbladis merged commit 7bf9a33 into nix-community:master Jul 31, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants