You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A project I work on follows the usual pattern of having two requirements file, one for production environments and one for development, compiled by pip-tools.
I just noticed that arrow adds the types-python-dateutil package to my prod requirements.txt.
Since typing information should not be necessary at runtime, I think the installation of that package should be left to the user who wants it.
The text was updated successfully, but these errors were encountered:
I also feel like this should be a development package. Perhaps it can be exposed as an optional extra arrow[dev] or arrow[types]? This way you can still make abstraction of your typing requirements for library users, while keeping it contained to those that specifically request it.
Feature Request
A project I work on follows the usual pattern of having two
requirements
file, one for production environments and one for development, compiled bypip-tools
.I just noticed that
arrow
adds thetypes-python-dateutil
package to my prodrequirements.txt
.Since typing information should not be necessary at runtime, I think the installation of that package should be left to the user who wants it.
The text was updated successfully, but these errors were encountered: