| 9 Nov 2023 |
 K900 | In reply to@k900:0upti.me
importlib.metadata.PackageNotFoundError: No package metadata was found for The 'safetensors>=0.3.1' distribution was not found and is required by this application.
^ | 19:17:07 |
 matthewcroughan - nix.how | Oh sorry, I didn't realise that was a quote in my client | 19:17:19 |
| matthewcroughan - nix.how | I thought it was juat a reply to my big log | 19:17:26 |
| matthewcroughan - nix.how | There are other programs in this python chain, that use the safetensors that is being provided correctly | 19:17:52 |
| matthewcroughan - nix.how | The first thing I did was put safetensors in the propagatedBuildInputs of eveyrthing I could think of | 19:18:12 |
| matthewcroughan - nix.how | it did not seem to change anything | 19:18:17 |
| matthewcroughan - nix.how | * The first thing I did was put safetensors in the propagatedBuildInputs of everything I could think of | 19:18:31 |
| matthewcroughan - nix.how | Why does safetensors have no metadata? That's what I don't understand. And how do I give it the metadata it needs? K900 ⚡️ | 19:21:49 |
| matthewcroughan - nix.how | safetensors = super.safetensors.overridePythonAttrs
(
old: {
sourceRoot = "safetensors-0.4.0/bindings/python";
cargoDeps = pkgs.rustPlatform.importCargoLock {
lockFile = ./nix/safetensors/Cargo.lock;
};
nativeBuildInputs = (old.nativeBuildInputs or [ ]) ++ [
pkgs.rustPlatform.cargoSetupHook
pkgs.rustPlatform.maturinBuildHook
];
}
);
| 19:21:54 |
| K900 | It doesn't have "no metadata" | 19:21:58 |
| K900 | It's missing something | 19:22:06 |
| matthewcroughan - nix.how | Oh, it can't find the package | 19:22:17 |
| matthewcroughan - nix.how | * Oh, it can't find the package? | 19:22:19 |
| K900 | You can try calling importlib.metadata.version("safetensors") in a Python shell yourself | 19:22:20 |
| matthewcroughan - nix.how | PackageNotFoundError | 19:22:23 |
| K900 | And see why it fails | 19:22:24 |
| matthewcroughan - nix.how | ls result/lib/python3.11/site-packages/safetensors_
safetensors_python-0.4.0.dist-info/ safetensors_rust/
| 19:24:05 |
| matthewcroughan - nix.how | grrr | 19:24:21 |
| matthewcroughan - nix.how | it's not ending up in the site-packages | 19:24:26 |
| matthewcroughan - nix.how | but the dist-info is | 19:24:44 |
| K900 | The dist-info is for safetensors_python | 19:25:56 |
| K900 | But the package it's looking for is safetensors | 19:26:04 |
| K900 | Have fun | 19:26:07 |
| matthewcroughan - nix.how | safetensors definitely gets built as part of building this application, I'm not sure why it doesn't end up in site-packages | 19:26:52 |
| matthewcroughan - nix.how | is it because the package is misnamed as safetensors_rust ? | 19:28:41 |
| matthewcroughan - nix.how | result/lib/python3.11/site-packages/safetensors_rust:
__init__.py __pycache__ safetensors_rust.cpython-311-x86_64-linux-gnu.so
| 19:28:48 |
| K900 | I don't know | 19:29:21 |
| matthewcroughan - nix.how | hmm nope, tokenizers is a rust binding that is built in the same way, and it is correctly positioned | 19:29:32 |
| matthewcroughan - nix.how | ls result/lib/python3.11/site-packages/tokenizers
tokenizers/ tokenizers_python-0.14.1.dist-info/
user: matthew 🌐 swordfish in privateGPT on main [!?⇡] is 📦 v0.1.0 via 🐍
✦ ❯ ls result/lib/python3.11/site-packages/tokenizers
__init__.py __pycache__ tokenizers.cpython-311-x86_64-linux-gnu.so
| 19:29:40 |
| K900 | Python package names and module names are not actually required to match | 19:29:43 |
