Thanks, I’m glad you mentioned this – we’ve actually been thinking about something similar! Our idea was to work with entry points. Your package could then define its recipes in the
entry_points, which would even let you drop the
-F argument completely. It’d also allow more complex and versioned recipe management, especially for larger teams using Prodigy.
I’ll also experiment with the PYTHONPATH solution, though – this could be a nice and simple addition in the meantime. If
-F is a valid path, Prodigy uses
importlib to load the recipe a file as a module. So in the case you describe, we could just skip that step and try to import it directly if it exists.