Lift closure cell update to earliest function - #461
Conversation
28cc2cf to
f177e5b
Compare
f177e5b to
ab3e8e3
Compare
|
Tested python-2.7, 3.7-3.11; |
|
All versions fail here: uqfoundation/mystic@f6f71f5 (as expected?) |
|
Sorry for the delay. I was unable to reproduce the error message on pypy3.9-v7.3.9-osx64. Perhaps, it was a bug within pypy that was fixed between 7.3.8 and 7.3.9. Can you try it again with the new version of pypy? As for mystic, I am still looking into it. I am getting this error message. Is this what you are seeing or are there additional errors? tests/__main__.py
Warning: Invalid termination condition (nPop < 2)
Warning: Invalid termination condition (nPop < 2)
Warning: Invalid termination condition (nPop < 2)
----------------------------------------------------------------------
Ran 32 tests in 3.695s
OK
----------------------------------------------------------------------
Ran 16 tests in 0.045s
OK
----------------------------------------------------------------------
Ran 16 tests in 0.072s
OK
----------------------------------------------------------------------
Ran 16 tests in 0.098s
OK
----------------------------------------------------------------------
Ran 16 tests in 3.403s
OK
Traceback (most recent call last):
File "/Users/ani/GitHub/mystic/tests/test_boundsconstrained.py", line 52, in <module>
test_constrained(NelderMeadSimplexSolver, tight=True, clip=None) #ftol=1e-8?
File "/Users/ani/GitHub/mystic/tests/test_boundsconstrained.py", line 48, in test_constrained
assert eval(_eqn) # constraint is satisfied
AssertionError
............................I don't think I made a change to either repo, and now 939d7aee and f6f71f5 work for me. I did make a couple of force pushes before ab3e8e3, so it is possible that you got an old version. I will still try to reproduce find out where that previous error came from. Can you please share the error message for mystic? |
|
You may be right. I just downloaded pypy v7.3.9, and will upgrade and run the With regard to The current |
|
There is an alternate to making updates to recover the previous behavior. We could, revert the previous behavior in |
|
I'll also work on getting you the error message I'm seeing with |
|
@mmckerns FYI. Using the call |
|
I believe the mystic code is an example of something that #448 tries to fix, not this PR. As of right now, I am still having trouble getting it to work, so there may be something deeper or some very small corner case that I missed. Will let you know. |
I'm assuming this is likely a historical artifact, but yes you are correct. |
I found the bug. It was that an |
This is a partial bug fix for #458. It covers most reasonable cases that were not covered in #443. See #458 for more details.