-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
DeprecationWarning for inspect.getargspec() raises Error/Fail in pytest-3.6 #6301
Comments
What is the full traceback? The given info does not point to any Astropy files, so it is hard to track the cause. |
I could track it down to lxml actually, not beautifulsoup as I had first suspected:
The real culprit is this function in lxml-3.8.0's
This might be their problem upstream then, as they should perhaps try |
One thing we can do on our side is to mark that test as @taldcroft , @bsipocz , or whoever interested to chime in -- What do you think? |
xfailing that one test for python3.6 sounds good to me. Please leave a descriptive note about the lxml version issue so we will have a chance to revisit when needed (and will also see why it xpasses the xfail...) |
Thought of |
Actually, instead of |
Unfortunately it seems difficult to catch the warning in the test.
made it look as it is promoted to an
|
Hmm, looks like it has something to do with the
directly from the
and after running the
Exactly the same in 3.5, except the tests do not fail... Ah, I think now I see why - at some point in the tests the general Any ideas if this is part of the |
Ohhhh! Yes, it is at https://github.com/astropy/astropy/blob/master/astropy/tests/helper.py#L139 . Since there is a precedent, there is no need to _warnings_to_ignore_by_pyver = {
# ...
(3, 6): set([
# Some note on why this was added
r"put the text here; see other entries for example"])
} |
Brilliant detective work! Indeed it works now. |
Just found it, too - yes, just requires a copy of @mdboom's fix for the 3.5 version. Whatever is easier - this is my patch:
|
It's your fix, so please push it, and we can merge when CI passed. |
Hope branching this from |
Oh, good that you say that, I haven't noticed. The base for every PR should be master, we'll do the backporting separately. |
PR is fixed up and can be merged once CI passed. |
Running the tests for 2.0rc1 I am seeing 24 failures reported, all apparently based on the same
Setup:
with
beautifulsoup 4.6.0
.The text was updated successfully, but these errors were encountered: