Warning on read-only filesystem: ndarray.pyi stub file could not be generated

[Lasall]

With numpydantic used in a read-only filesystem (e.g. docker container), I get the following warning:

/usr/local/lib/python3.12/site-packages/numpydantic/meta.py:66: UserWarning: ndarray.pyi stub file could not be generated: [Errno 30] Read-only file system: '/usr/local/lib/python3.12/site-packages/numpydantic/ndarray.pyi'
   warn(f"ndarray.pyi stub file could not be generated: {e}", stacklevel=1)

It would be nice to optionally disable the creation of typing information or limit it to type checkers only.

Probably the warning exists also when numpydantic is installed as root system library and then an application executes it as a user.

[sneakers-the-rat]

aha, yeah that being autogenerated on import was intended to facilitate plugins (rather than versioning the .pyi, if there is some plugin present in the environment, the .pyi will reflect that, etc.), but that's mostly a "leaving an opening for the future" thing for now. Root cause is ultimately the nptyping (non-python-typing) system we inherited that will be replaced in 2.0.

I had been holding off setting up env config models and loggers because it didn't seem like the project needed them yet, and i would like to do that with a bit of care. Don't have time to do that this week, but for now i'll just flip that to an ImportWarning which is ignored by default and thus shouldn't be printed in the context in that issue of just running the dockerfile.

would that work? otherwise i can handle proper logging and env config next week

[sneakers-the-rat]

lmk if that doesn't work/isn't what you needed <3

[Lasall]

Thank you so much, your fix works perfectly fine for me!