History of changes to
‘Disable Python package check in Nix’

2025-09-02





> 2025-04-17: Add rights to post and notes, see 61ee3af

diff --git a/note/disable-python-package-eck-in-nix.md b/note/disable-python-package-eck-in-nix.md
index 949dae7..4d3f10a 100644
--- a/note/disable-python-package-eck-in-nix.md
+++ b/note/disable-python-package-eck-in-nix.md
@@ -4,6 +4,7 @@ date: 2025-04-02
 lange: en
 description: "Disable Python package check in Nix"
 keywords: nix python
+rights: CC0 1.0
 ---
 
 When deploying Python service to staging using Nix, I want to disable




> 2025-04-04: Add keywords

diff --git a/note/disable-python-package-eck-in-nix.md b/note/disable-python-package-eck-in-nix.md
index 03ef0af..949dae7 100644
--- a/note/disable-python-package-eck-in-nix.md
+++ b/note/disable-python-package-eck-in-nix.md
@@ -3,6 +3,7 @@ title: "Disable Python package check in Nix"
 date: 2025-04-02
 lange: en
 description: "Disable Python package check in Nix"
+keywords: nix python
 ---
 
 When deploying Python service to staging using Nix, I want to disable




> 2025-04-04: Add lang and description to posts and notes

diff --git a/note/disable-python-package-eck-in-nix.md b/note/disable-python-package-eck-in-nix.md
index 0938f6d..03ef0af 100644
--- a/note/disable-python-package-eck-in-nix.md
+++ b/note/disable-python-package-eck-in-nix.md
@@ -1,6 +1,8 @@
 ---
 title: "Disable Python package check in Nix"
 date: 2025-04-02
+lange: en
+description: "Disable Python package check in Nix"
 ---
 
 When deploying Python service to staging using Nix, I want to disable




> 2025-04-03: Expand 0e8b8c2 with source

diff --git a/note/disable-python-package-eck-in-nix.md b/note/disable-python-package-eck-in-nix.md
index d568d25..0938f6d 100644
--- a/note/disable-python-package-eck-in-nix.md
+++ b/note/disable-python-package-eck-in-nix.md
@@ -6,6 +6,19 @@ date: 2025-04-02
 When deploying Python service to staging using Nix, I want to disable
 checks for that Python package. (Checks already happened in CI anyway.)
 
+Obvious question is *how*; obvious answer is *overrides*. Then, let me
+reformulate that obvious question a bit: *which one?*
+
+Giving up on the documentation, the [nixpkgs source][] is a bit helpful:
+
+> Derivations built with `buildPythonPackage` can already be overridden
+> with `override`, `overrideAttrs`, and `overrideDerivation`.
+
+> This function introduces `overridePythonAttrs` and it overrides the
+> call to `buildPythonPackage`.
+
+[nixpkgs source]: https://github.com/NixOS/nixpkgs/blob/52fb9fdcf08726630284310461f2517e4ecee830/pkgs/development/interpreters/python/python-packages-base.nix#L15
+
 This is the relevant overlay:
 
 ``` nix
go back see note