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
One of the tests in the test suite is broken: the expectation for the creation_date field is to have a list of two dates.
This is actually a bug in the behaviour of the .ua parser : we're getting the correct creation date, but additionally we're also grabbing the creation_date of one of the contacts in the response.
Here's an example of this happening. In the whois response, we should only be expecting to see datetime.datetime(2002, 12, 4, 0, 0) as a response, but there is an additional one:
The regexp for creation_date in WhoisUA needs to be made stricter so that it only catches the first occurence of ^created:. However, I tried to use the following but it didn't work. From what I understand, WhoisEntry.parse() ends up using re.findall() which make the back reference totally useless.
One of the tests in the test suite is broken: the expectation for the
creation_date
field is to have a list of two dates.This is actually a bug in the behaviour of the .ua parser : we're getting the correct creation date, but additionally we're also grabbing the creation_date of one of the contacts in the response.
Here's an example of this happening. In the whois response, we should only be expecting to see
datetime.datetime(2002, 12, 4, 0, 0)
as a response, but there is an additional one:The regexp for
creation_date
in WhoisUA needs to be made stricter so that it only catches the first occurence of^created:
. However, I tried to use the following but it didn't work. From what I understand,WhoisEntry.parse()
ends up usingre.findall()
which make the back reference totally useless.I'm stumped about how to fix this.
The text was updated successfully, but these errors were encountered: