-
Notifications
You must be signed in to change notification settings - Fork 1.5k
kill unwrapped_remote #1490
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
kill unwrapped_remote #1490
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -63,12 +63,10 @@ class ExecTestLogger(Plugin): | |
async def beforePyScriptExec(self, interpreter, src, pyScriptTag): | ||
console.log(f'beforePyScriptExec called') | ||
console.log(f'before_src:{src}') | ||
console.log(f'before_id:{pyScriptTag.id}') | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I have removed this for now...since it wasn't testing something of any significant value I guess... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. pyScriptTag should be unwrapped as an HtmlElement within Python, and not appear like a JsProxy in this context... I was having similar issues with the event listener work, with some methods/attributes on JsProxies not proxying properly. We should try to understand why this regression happened, because it means something in the way the JS objects are proxied into Python is broken. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I'm confused. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I phrased my response poorly. This is my concern:
Accessing the Specific to this code, does this mean users can't access attributes of the |
||
|
||
async def afterPyScriptExec(self, interpreter, src, pyScriptTag, result): | ||
console.log(f'afterPyScriptExec called') | ||
console.log(f'after_src:{src}') | ||
console.log(f'after_id:{pyScriptTag.id}') | ||
console.log(f'result:{result}') | ||
|
||
|
||
|
@@ -88,12 +86,10 @@ class PyReplTestLogger(Plugin): | |
def beforePyReplExec(self, interpreter, src, outEl, pyReplTag): | ||
console.log(f'beforePyReplExec called') | ||
console.log(f'before_src:{src}') | ||
console.log(f'before_id:{pyReplTag.id}') | ||
|
||
def afterPyReplExec(self, interpreter, src, outEl, pyReplTag, result): | ||
console.log(f'afterPyReplExec called') | ||
console.log(f'after_src:{src}') | ||
console.log(f'after_id:{pyReplTag.id}') | ||
console.log(f'result:{result}') | ||
|
||
|
||
|
@@ -261,9 +257,7 @@ def test_pyscript_exec_hooks(self): | |
# These could be made better with a utility function that found log lines | ||
# that match a filter function, or start with something | ||
assert "before_src:x=2; x" in log_lines | ||
assert "before_id:pyid" in log_lines | ||
assert "after_src:x=2; x" in log_lines | ||
assert "after_id:pyid" in log_lines | ||
assert "result:2" in log_lines | ||
|
||
@skip_worker("FIXME: relative paths") | ||
|
@@ -286,9 +280,7 @@ def test_pyrepl_exec_hooks(self): | |
# These could be made better with a utility function that found log lines | ||
# that match a filter function, or start with something | ||
assert "before_src:x=2; x" in log_lines | ||
assert "before_id:pyid" in log_lines | ||
assert "after_src:x=2; x" in log_lines | ||
assert "after_id:pyid" in log_lines | ||
assert "result:2" in log_lines | ||
|
||
@skip_worker("FIXME: relative paths") | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed
callKwargs
to have actual list of args instead....There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to make it so that we can use
kwargs
. I'll look into fixing it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea @madhur-tandon, it looks also cleaner and easier to read now
yes, this looks like a good idea in general