Hi, I’m trying to set up my own extensions packag...
# ask-metaflow
f
Hi, I’m trying to set up my own extensions package. Been following https://github.com/Netflix/metaflow-extensions-template and https://github.com/Netflix/metaflow-nflx-extensions/tree/main as examples, but when I set my extensions package as a dependency, I’m not able to locate it within the installed modules paths, under
metaflow_extensions/
. Not exactly sure if its due to an issue with my package structure / naming or my build setup. Any help would be greatly appreciated! My package structure looks like:
Copy code
metaflow_extensions/my_org
├── config
│   └── mfextinit_my_org.py
├── plugins
│   ├── mfextinit_my_org.py
│   │  
│   ├── metadata
│   │   ├── service_file.py
│   │   └── __init__.py
│   │
│   ├── utils
│   │   ├── util_file.py
│   │   └── __init__.py
│   │
└── toplevel
    └── mfextinit_my_org.py
    └── toplevel.py
and my pyproject.toml is defined:
Copy code
[build-system]
requires = [
    "setuptools >= 61",
    "wheel",
]

build-backend = "setuptools.build_meta"

[project]
name = "my_org_metaflow_ext"
version = "1.0"
readme = "README.md"
requires-python = ">=3.10,<3.11"
classifiers = [
    "Programming Language :: Python :: 3.10",
]

#[tool.setuptools.packages.find]
where = ["src/"]
include = ["metaflow_extensions.my_org"]

[tool.setuptools]
py-modules = ["metaflow_extensions"]

# Specify your dependencies here.
dependencies = [
    "metaflow >= 2.10.8"
]
d
hey — could you do
METAFLOW_DEBUG_EXT=1 python -c "import metaflow"
and send the output (or put it somewhere I can check it out)
f
Placed it under https://qtext.io/3gst thanks for taking a look
d
maybe i am missing something but I don’t see anything there.
f
How about now?
d
ah now I see something
are you with @wooden-dusk-90720? Related to that other question he DMd me? It looks like it is finding your extension but it doesn’t see any of the files/extensions in the right place it looks like. COuld you see what files are in your wheel?
w
hey yea we're on the same team, but i think we're good now. we'll reach out again if we encounter other issues
d
cool — it looked slightly different from the messages but close enough 🙂. Sure thing. And I haven’t forgotten about your other issue of building directory packages but haven’t had a chance to look at that yet.
w
so on that one, we're currently doing a symlink and reading the dependencies from the pyproject.toml to put into the flow decorator (with some modifications to remove things like "^" and python). it's kind of annoying but will get us by for now