You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Started noticing failures with pytest 8.1.0.dev171+g9454fc38d. I suspect it is caused by #11804 .
In astropy , we have a warning class that is a grandchild of Python built-in Warning class, defined as follows (don't ask me why, I am just the messenger):
classIllegalMinuteWarning(AstropyWarning):
""" Raised when a minute value is 60. Parameters ---------- minute : int, float """def__init__(self, minute, alternativeactionstr=None):
self.minute=minuteself.alternativeactionstr=alternativeactionstrdef__str__(self):
message= (
f"'minute' was found to be '{self.minute}', which is not in range [0,60)."
)
ifself.alternativeactionstrisnotNone:
message+=" "+self.alternativeactionstrreturnmessage
Works fine for years, until today. I think pytest type check is now too strict. Is this something you are able to relax a little on your end? Thanks!
I'd agree that not accepting a Warning as reported in #11959 looks like a bug, but for numerical inputs this makes more sense, and would be fairly easy to fix on the Astropy side.
Started noticing failures with
pytest 8.1.0.dev171+g9454fc38d
. I suspect it is caused by #11804 .In astropy , we have a warning class that is a grandchild of Python built-in
Warning
class, defined as follows (don't ask me why, I am just the messenger):Works fine for years, until today. I think pytest type check is now too strict. Is this something you are able to relax a little on your end? Thanks!
Detailed log and more info here:
The text was updated successfully, but these errors were encountered: