Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't force requirement on types-python-dateutil #1169

Open
mredaelli opened this issue Jan 8, 2024 · 2 comments
Open

Don't force requirement on types-python-dateutil #1169

mredaelli opened this issue Jan 8, 2024 · 2 comments

Comments

@mredaelli
Copy link

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 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.

@bnavigator
Copy link

bnavigator commented Jan 12, 2024

As a contributor to the maintenance of the openSUSE Tumbleweed Linux Python Stack, I wholeheartedly agree.

https://build.opensuse.org/request/show/1138316

@sanderr
Copy link

sanderr commented Mar 29, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants