| 12 May 2026 |
hexa | Redacted or Malformed Event | 14:27:29 |
hexa | hm, without mypyc, indeed | 14:28:00 |
hexa | diff --git a/pkgs/build-support/rust/fetch-cargo-vendor.nix b/pkgs/build-support/rust/fetch-cargo-vendor.nix
index 2802bf9e73f1..f97c270e731a 100644
--- a/pkgs/build-support/rust/fetch-cargo-vendor.nix
+++ b/pkgs/build-support/rust/fetch-cargo-vendor.nix
@@ -3,7 +3,7 @@
stdenvNoCC,
runCommand,
writers,
- python3Packages,
+ python3,
cargo,
gitMinimal,
nix-prefetch-git,
@@ -11,6 +11,14 @@
}:
let
+ python = python3.override {
+ self = python;
+ packageOverrides = final: prev: {
+ charset-normalier = prev.charset-normalizer.override { withMypyc = false; };
+ };
+ };
+ python3Packages = python.pkgs;
+
replaceWorkspaceValues = writers.writePython3Bin "replace-workspace-values" {
libraries = with python3Packages; [
tomli
diff --git a/pkgs/development/python-modules/charset-normalizer/default.nix b/pkgs/development/python-modules/charset-normalizer/default.nix
index 5137ceb0e83f..c3650a402f17 100644
--- a/pkgs/development/python-modules/charset-normalizer/default.nix
+++ b/pkgs/development/python-modules/charset-normalizer/default.nix
@@ -8,6 +8,7 @@
pytestCheckHook,
requests,
setuptools,
+ withMypyc ? !isPyPy,
}:
buildPythonPackage rec {
@@ -30,9 +31,9 @@ buildPythonPackage rec {
build-system = [
setuptools
]
- ++ lib.optional (!isPyPy) mypy;
+ ++ lib.optional (withMypyc) mypy;
- env.CHARSET_NORMALIZER_USE_MYPYC = lib.optionalString (!isPyPy) "1";
+ env.CHARSET_NORMALIZER_USE_MYPYC = lib.optionalString (withMypyc) "1";
nativeCheckInputs = [ pytestCheckHook ];
| 14:33:05 |
hexa | Redacted or Malformed Event | 14:33:10 |
emily | wonder if it makes sense to RIIR the fetcher so that the cycle can be broken locally | 14:33:26 |
hexa | hm, not quite yet escaped the infinite recursion | 14:36:13 |
figsoda | hexa u had a typo in charset-normalizer in your patch | 14:51:32 |
hexa | thanks for checking :D | 14:51:41 |
hexa | yeah, that works | 14:52:10 |
figsoda | that sounds like the better plan in the long term, but it will still need some bootstrapping (within rust stuff) to work, so you don't have cargo -> fetchCargoVendor -> importCargoLock -> cargo | 14:58:08 |
Toma | BTW we can also still revive fetchCargoTarball (aka. the internal cargo vendor logic) for internal use only | 20:05:01 |
| 13 May 2026 |
Pol | I am working onto packaging oxc and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. | 13:15:30 |
Pol | * I am working onto packaging oxc and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. Is there a trick I could do to restart the build where it was, some kind of "during development mode", just for writing the package.nix file correctly. | 13:41:19 |
Pol | * I am working onto packaging oxc and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. Is there a trick I could do to restart the build where it was, some kind of "during development mode", just for writing the package.nix file correctly ? | 13:41:27 |
Pol | * I am working onto packaging oxc (https://github.com/oxc-project/oxc) and the build is very long and it seems that there are a couple of failing tests. Do you have some advice to share to speed up the process ? Currently, I just run nix-build -A oxc then wait 30 minutes, then modify the package.nix file, adding a --skip=... line, then repeat. Is there a trick I could do to restart the build where it was, some kind of "during development mode", just for writing the package.nix file correctly ? | 13:49:40 |
figsoda | oxc is a monorepo of different tools, we already have oxfmt and oxlint in nixpkgs, what specifically are you looking to package? | 13:57:22 |
Pol | Oooh it's in there already, shit I must not have seen it | 13:57:48 |
figsoda | and for development i believe you can nix-shell or nix develop and run the hooks yourself manually | 13:57:57 |
Pol | #facepalm... | 13:58:04 |
Pol | Thank you | 13:58:06 |
| 14 May 2026 |
| @pederbs:pvv.ntnu.no left the room. | 00:23:10 |
| @puercopop:matrix.org left the room. | 03:52:30 |
| @tjni:matrix.org left the room. | 04:57:54 |
| Pol changed their display name from Pol to Pol (out, touching grass). | 07:37:49 |
| Pol changed their display name from Pol (out, touching grass) to Pol. | 16:31:46 |
EsperLily [she/her] | Alyssa Ross: apologies for losing track of this PR for a while but I just replied to your comment on https://github.com/NixOS/nixpkgs/pull/510169 (cargo: remove runtime references to cargo-bootstrap). I don't currently have a good way to actually keep up with github stuff (since github notifications don't work very well) beyond just remembering to look at any open PRs, so feel free to poke me if I lose track again | 22:51:02 |