Where does prefect decide which packages to install?

Hi eddy, for installation here: https://github.com/PrefectHQ/prefect/blob/main/setup.py https://github.com/PrefectHQ/prefect/blob/main/requirements.txt

Does it work with

pyproject.toml

?

My understanding is that

pyproject.toml

supplants

setup.py

, which currently our repository is not configured for

Ye it keeps everything nicely in one file, I will open a feature enhancement

Sorry I’m confused about how the internal file we are using affects your usage

Oh I got the two mixed up, how do I tell prefect to install from my

pyproject.toml

my kubernetes deployment is erroring on package not found?

The most common pattern is to create an image based on the Prefect image with your project installed.

When specifying that image I create in my

kubernetes-job

block here, will it be looking on docker hub, so something like 'eddywd/prefect_pandas'?

You could push it to DockerHub or make it available on a registry on Kubernetes / GCP / etc. depending on your infrastructure.

My

pyproject.toml

was created to work with poetry and so has this in the build systems:

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

Does that need to be changed to setup tools:

[build-system]
requires = ["setuptools>=61.0"]
build-backend = "setuptools.build_meta"

to match the base prefect image?

The Prefect base image doesn’t care what tool you’re using to build your project

Great thanks