-
Notifications
You must be signed in to change notification settings - Fork 29
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
Conflict with marshmallow install #9
Comments
+1 on this. Big hinderance when trying to use |
+1. Current implementation leads to unpredictable builds and makes it frustrating to use toasted marshmallow. |
+1 also running into this bug. |
This really is bad practice. You guys should fork marshmallow, not overwrite it. This is not a drop-in replacement for marshmallow - it broke my project (as mentioned above - sqlalchemy-marshmallow). Even when I disabled toasted marshmallow's version of jit, my project was still broken, and I had to force reinstall marshmallow to get it working again. Had I not seen this issue, it may have taken a long time to figure out what happened and how to fix. |
Kind of mad this ever happened and madder still that it hasn't been fixed and no one has responded. Use pydantic instead. It's faster than toasted-marshmallow and more elegant IMHO. |
Currently toasted-marshmallow is messing with the marshmallow install and causing errors. I'm pretty sure that modifying other named packages in
site-packages/
is pretty bad form.It should either use the system version of marshmallow (perhaps with constraints on which version) or install a custom version of marshmallow somewhere else.
Current behaviour:
Try uninstalling
toasted-marshmallow
and you get:In other works
toasted-marshmallow
is installing it's own version ofmarshmallow
tosite-packages/marshmallow
, then I'm getting an error if I install the real marshmallow:(I want both
marshmallow
andtoastedmarshmallow
installed for my benchmarks of other frameworks)The text was updated successfully, but these errors were encountered: