| 6 Feb 2024 |
 @phaer:matrix.org | Going by the paths alone, it looks like py3rosmsgs vendors genpy, so you'd end up with two versions of that module in PYTHON_PATH.
| 09:01:53 |
| @phaer:matrix.org | * Going by the paths alone, it looks like py3rosmsgs vendors genpy, so you'd end up with two versions of that module in PYTHONPATH. | 09:01:57 |
 gaivs | In reply to @phaer:matrix.org
Going by the paths alone, it looks like py3rosmsgs vendors genpy, so you'd end up with two versions of that module in PYTHONPATH. Yeah that makes sense. Do you know how I'd try to fix this? Can I remove the vendor somehow for py3rosmsgs? | 09:26:45 |
| @phaer:matrix.org | You could do that the same way you removed the non-vendored version via postInstall above. Would recommend to check why it's vendored first ;) | 09:31:09 |
| gaivs | Just removing it from genpy makes it work, no idea why they are vendored though, and don't really know what to look for, could you give me a pointer? 😅 | 10:01:28 |
| @phaer:matrix.org | Not the easiest question, as I don't know either of those packages. Could be that it's just to ease distribution, could also be that they are vendoring a patched version. First thing to check could be whether the vendored genpy is actually different from the upstream one.
Or just asking py3rosmsgs maintainers about it | 10:23:11 |
| gaivs | py3rosmsgs doesn't seem to depend on genpy, though it has a module called genpy... I wonder if this is due to a naming crash?
The annoying thing is that what I'm actually depending on here is the rosnumpy package, which is the one that in the end brings in genpy and py3rosmsgs, so there are, annoyingly, multiple levels of separation | 12:08:53 |
| @phaer:matrix.org | Oh, i see. That's unfortunate. Python packages aren't namespaced by their distribution name, so python can't really distinguish between the module called genpy exposed by py3rosmgs, and the one exposed by genpy itself | 14:28:58 |
| gaivs | Ah ok, yeah that is unfortunate... Oh well, there's not much I can do about this, if I run into problems because of this, I'll just have to remove that rosnumpy package | 15:35:15 |
| gaivs | Thanks for all the help btw! | 15:35:17 |
| 8 Feb 2024 |
|  @niklauzg:matrix.org joined the room. | 04:28:22 |
 l0b0 | adisbladis: Do you have time to look into https://github.com/nix-community/poetry2nix/issues/1459? I don't seem to be able to combine any recent versions of poetry2nix and nixpkgs. | 20:18:39 |
| 15 Feb 2024 |
|  xescure joined the room. | 15:16:37 |
| xescure | Does this ring a bell to anyone? > flit_core.config.ConfigError: Neither [project] nor [tool.flit.metadata] found in pyproject.toml
| 15:17:51 |
| xescure | I've been trying to convert my flask API to a nix deployment, but I get this error when trying to install my dependencies | 15:18:33 |
| xescure | I had some problems with missing setuptools, but I solved that with the help of the FAQ | 15:19:07 |
| xescure | * | 15:19:22 |
 @djacu:matrix.org | I know it's not the same error message but does adding it as a build input in the overrides fix it?
https://github.com/nix-community/poetry2nix/issues/606 | 15:22:32 |
