Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ModelSchema.load(instance=None) call wont overridden .instance
See original GitHub issueas in ModelSchema.load
self.instance = instance or self.instance
because I instantiation schema class in module level, reuse them in multiple places and across requests,
the .instance value firstly set will persists in following load() calls, regardless load(instance=None), this will trigger nasty bug as its value depends on request order.
is there a good reason for this behavior and not just set self.instance from parameter?
or should I instantiation a new schema object before any load or dump call?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve just released 0.12.1, which should fix this bug. Thanks for reporting! Please reopen this if the issue persists.
I’m experiencing the same problem and it costs me the whole afternoon. I feel there’s no point keeping the instance on the schema.