-
Notifications
You must be signed in to change notification settings - Fork 96
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
Spring items break pickling with Traits 5.0.0 #514
Comments
Hi, thanks for the report. This looks like it is related to enthought/traits#452 The immediate workaround would be to downgrade your version of Traits to 4.6.0 (or github master prior to 23rd Dec 2018/commit eecc23d6 if there are bugfixes you need). |
I'm going to tentatively close the issue for now, since it is a duplicate of |
Forgot to mention I am running Python 3.7.1 on Windows 10 64bit. Thank you |
If you still see the issue with Traits 4.6.0 please re-open the ticket. If not, maybe add your observations to the traits issue as an extra data point. |
Hmm. On closer inspection, this does look like a new variant of enthought/traits#452. It's not clear to me whether it should be a separate issue or not. |
The issue is not present with v4.6.0, it appeared after update to 5.0.0 I leave up to you whether you'd like to re-open this or merge it with enthought/traits#452 Thanks! |
So it's almost certainly a Traits issue rather than a Traits UI one - let's leave it closed here. I'll try to find time to investigate on the Traits side soon, and if necessary I'll split enthought/traits#452 into two issues then. Thanks for the report! |
I encountered a strange behaviour while pickling traits with Traits 5.0.0 and Traitsui 6.0.0
If one trait contains an instance of another trait, whose view contains a Spring item, pickling results in an error.
In the following code, if one comments out the spring item in the view of the MyTrait the code works correctly, otherwise results in an error.
Most likely related to: enthought/traits#447
Expected output:
Error
The text was updated successfully, but these errors were encountered: