Skip to content

for issue 429 #433

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

Closed
wants to merge 12 commits into from
Closed

for issue 429 #433

wants to merge 12 commits into from

Conversation

ramvikrams
Copy link
Contributor

Copy link
Collaborator

@Dr-Irv Dr-Irv left a comment

Choose a reason for hiding this comment

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

See here:

FutureWarning, match="Not prepending group keys", upper="1.5.99"

for an example of how to use pytest_warns_bounds. You need to specify the upper parameter

@ramvikrams
Copy link
Contributor Author

See here:

FutureWarning, match="Not prepending group keys", upper="1.5.99"

for an example of how to use pytest_warns_bounds. You need to specify the upper parameter

Yes sir

@ramvikrams
Copy link
Contributor Author

See here:

FutureWarning, match="Not prepending group keys", upper="1.5.99"

for an example of how to use pytest_warns_bounds. You need to specify the upper parameter

Yes sir

Still not getting the checks passed after adding upper

@Dr-Irv
Copy link
Collaborator

Dr-Irv commented Nov 20, 2022

Still not getting the checks passed after adding upper

Use pytest_warns_bounds() not python_warns_bounds(). When checks fail, look at the results of the checks to see the error messages.

But before you push, you should test locally by running poetry run poe test to see if the tests pass on your machine

@ramvikrams
Copy link
Contributor Author

Still not getting the checks passed after adding upper

Use pytest_warns_bounds() not python_warns_bounds(). When checks fail, look at the results of the checks to see the error messages.

But before you push, you should test locally by running poetry run poe test to see if the tests pass on your machine

Yes sir

@ramvikrams
Copy link
Contributor Author

It is still saying undefined name pytest_warns_bounds

@Dr-Irv
Copy link
Collaborator

Dr-Irv commented Nov 20, 2022

It is still saying undefined name pytest_warns_bounds

It means you didn't import it. Look at other examples. This is basic python programming.

@ramvikrams
Copy link
Contributor Author

It is still saying undefined name pytest_warns_bounds

It means you didn't import it. Look at other examples. This is basic python programming.

Sir what is the module to import pytest_warns_bounds i coudn't find it.

@Dr-Irv
Copy link
Collaborator

Dr-Irv commented Nov 21, 2022

It is still saying undefined name pytest_warns_bounds

It means you didn't import it. Look at other examples. This is basic python programming.

Sir what is the module to import pytest_warns_bounds i coudn't find it.

Sorry it is pytest_warns_bounded not pytest_warns_bounds . Look at test_frame.py for an example

@ramvikrams
Copy link
Contributor Author

It is still saying undefined name pytest_warns_bounds

It means you didn't import it. Look at other examples. This is basic python programming.

Sir what is the module to import pytest_warns_bounds i coudn't find it.

Sorry it is pytest_warns_bounded not pytest_warns_bounds . Look at test_frame.py for an example

yes sir

@ramvikrams
Copy link
Contributor Author

Done sir

Copy link
Collaborator

@Dr-Irv Dr-Irv left a comment

Choose a reason for hiding this comment

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

You changed WAY too many tests. Only change the ones listed in the original issue.

@ramvikrams
Copy link
Contributor Author

You changed WAY too many tests. Only change the ones listed in the original issue.

yes sir

@ramvikrams
Copy link
Contributor Author

You changed WAY too many tests. Only change the ones listed in the original issue.

Done sir

Copy link
Collaborator

@Dr-Irv Dr-Irv left a comment

Choose a reason for hiding this comment

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

This is trickier than I thought. You have to look at the 6 failures in the nightly CI and we have to put in something where if the pandas version is larger than the bound specified, we catch an exception rather than trap a warning. I think the right solution is to modify the implementation of pytest_warns_bounded to return a different context manager if the version of pandas is >= the upper bound such that the context manager is trapping the exception. Use contextlib.supprress() and you'd have to pass in the expected exception type.

This is non-trivial. I'm not sure you will be able to do it. If not, let me know, and I will take this over.

@ramvikrams
Copy link
Contributor Author

contextlib.supprress()

I think it would be better if you take over.

@Dr-Irv Dr-Irv mentioned this pull request Nov 22, 2022
1 task
@Dr-Irv
Copy link
Collaborator

Dr-Irv commented Nov 22, 2022

closing in favor of #436

@Dr-Irv Dr-Irv closed this Nov 22, 2022
@ramvikrams
Copy link
Contributor Author

closing in favor of #436

yes sir

@ramvikrams ramvikrams deleted the T3 branch November 23, 2022 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nightly build appears to be broken
2 participants