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

Fix extended trait change issues #621

Closed
wants to merge 2 commits into from

Conversation

corranwebster
Copy link
Member

This fixes #537 and fixes #538.

It also removes expected failures of tests.

This may break existing code that accidentally uses buggy behaviour.

@codecov-io
Copy link

codecov-io commented Dec 4, 2019

Codecov Report

Merging #621 into master will increase coverage by 0.33%.
The diff coverage is 60%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #621      +/-   ##
==========================================
+ Coverage   69.43%   69.76%   +0.33%     
==========================================
  Files          40       40              
  Lines        6282     6285       +3     
  Branches     1295     1296       +1     
==========================================
+ Hits         4362     4385      +23     
+ Misses       1521     1501      -20     
  Partials      399      399
Impacted Files Coverage Δ
traits/traits_listener.py 80.04% <60%> (+0.95%) ⬆️
traits/trait_types.py 66.33% <0%> (-0.17%) ⬇️
traits/has_traits.py 70.3% <0%> (+0.16%) ⬆️
traits/traits.py 61.25% <0%> (+1.29%) ⬆️
traits/etsconfig/etsconfig.py 63.58% <0%> (+6.17%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 761d76d...74c2179. Read the comment docs.

@mdickinson
Copy link
Member

As a data point, this is causing a significant number of test failures on a largish Traits-using project; some repetitions, but it looks like 10-15 different instances of failure.

Copy link
Member

@mdickinson mdickinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the extent of the breakage seen in testing, I don't think we can get this into 6.0.0. We need to find some way to provide a non-breaking upgrade-path for Traits-using applications.

@mdickinson
Copy link
Member

@corranwebster Thoughts on what to do with this PR? We can leave it open and use it as a starting-point for more far-reaching updates. Or should it be closed?

@corranwebster
Copy link
Member Author

I think it needs to be closed sooner or later: I think we've demonstrated that too much downstream code will be broken by this change.

Certainly we don't want an accidental merge.

@mdickinson
Copy link
Member

Closing here; I've left a couple of comments on #537 and #538 pointing to this PR and explaining why it wasn't used as the fix.

@mdickinson mdickinson closed this Jan 3, 2020
@mdickinson mdickinson deleted the fix/extended-trait-change-errors branch January 3, 2020 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants