-
-
Notifications
You must be signed in to change notification settings - Fork 286
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
Simplify dependency graph #1365
Comments
Care to provide additional detail and a proposal? E.g. what can be removed and what part of the codebase would need to be refactored? |
I appreciate the developers in what they created. I have exactly the same situation as @ulfaslakprecis in my org. Having all dev dependencies in the requirements, means that if we want to productionize it, we will need to create enormous containers just to perform a simple validation. Not all the functionalities are needed for the core, and in terms of other teams that's a clear no go. There are lot's of dependencies management tools (like poetry, or pip-tools), that besides other optionalities target this issue. If you want to go for a native pip solution it is possible as well: |
Happy to support work on making pandera more light-weight. @ulfaslakprecis any appetite for contributing to pandera as opposed to building + maintaining a brand new project? |
Also wanted to better-understand the issue here. The items listed in the dependency graph are not necessarily what you get when you Without installing all of the extras, the packages installed are listed here: That said, I do think we could get rid of
@GOGKI just so I understand this, do you only need to install core pandera when you need to productionize your code? What unexpected/unwanted dependencies do you get? |
same question to you @ulfaslakprecis. What dependencies do you consider too heavy weight in your pandera installation (not the dependency graph reported by github, but the ones that are actually installed when you |
@cosmicBboy in our case we are having issues with typeguard. Pandera uses typeguard>=3.0.2 and jaxtyping uses typeguard==2.13.3 which makes them incompatible. So having typeguard as an optional dependency would possibly fix the problem. Allowing typeguard 2 would also fix our problem. |
@ulfaslakprecis any comments on #1365 (comment)? If not gonna close this issue in the next few days. Created
To capture slimming down the dependencies of a bare pandera installation, but the initial claim in this issue
is actually a non-issue, since the github-reported dependency graph naively reports dependencies in requirements files and not actually the dependencies entailed by |
Closing now |
Is your feature request related to a problem? Please describe.
We want to use Pandera in our organization's codebase, but a some evaluation deemed it unusable at the moment, due to the ENORMOUS (213 pages long) dependency graph.
Describe the solution you'd like
I think A LOT of dependencies can be removed.
Additional context
I used Pandera in one project and loved it. Tried to push it to the rest of the org as an alternative to Pydantic.
The text was updated successfully, but these errors were encountered: