"code" argument must be single file (expect for "package")?

[cpierceworld]

I'm trying to include custom components that I have defined in multiple files and include them with the "code" command line argument.

Problem is only "package" accepts a comma separated list of files. The rest only accept 1 file ("train", "pretrain", "evaluate" and "assemble").

Does anyone know if there is a particular reason for that?

I really don't want to put all my components into one monolithic file.
(Or better for me would be to specify the root folder of a python package and have it use/copy the whole package)

[thomashacker]

Hello,
For these commands (train, pretrain, evaluate, and assemble) you'll only need one .py file which just imports the custom code. For the package command however, you need to include every custom code file to the CLI.

The Healthsea spaCy project is a good example for that:

• CLI command for train
• Custom code file for train
• CLI command for packaged

[vitorbaptista]

Is this something you'd consider changing (or accepting a PR that does so)?

Currently, I need to create a single file that imports every required file just for the train, pretrain, etc., while in package I can just import everything directly. Is there a reason for this inconsistency?

[thomashacker]

Yes, this is something we're considering changing in the future, and we're happy to accept a PR for that.