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
Copy file name to clipboardExpand all lines: README.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,12 @@ The manual (including install instructions) can be found in the doc/ directory.
29
29
* Nameservers
30
30
* Optional WHOIS data normalization
31
31
* Attempts to intelligently reformat WHOIS data for better (human) readability
32
+
* Converts various abbreviation types to full locality names
33
+
* Airport codes
34
+
* Country names (2- and 3-letter ISO codes)
35
+
* US states and territories
36
+
* Canadian states and territories
37
+
* Australian states
32
38
*`pwhois`, a simple WHOIS tool using pythonwhois
33
39
* Easily readable output format
34
40
* Can also output raw WHOIS data
@@ -39,6 +45,8 @@ The manual (including install instructions) can be found in the doc/ directory.
39
45
40
46
## Important update notes
41
47
48
+
*2.4.0 and up*: A lot of changes were made to the normalization, and the performance under Python 2.x was significantly improved. The average parsing time under Python 2.7 has dropped by 94% (!), and on my system averages out at 18ms. Performance under Python 3.x is [unchanged](https://github.com/joepie91/python-whois/issues/27). `pythonwhois` will now expand a lot of abbreviations in normalized mode, such as airport codes, ISO country codes, and US/CA/AU state abbreviations. The consequence of this is that the library is now bigger (as it ships a list of these abbreviations). Also note that there *may* be licensing consequences, in particular regarding the airport code database. More information about that can be found below.
49
+
42
50
*2.3.0 and up*: Python 3 support was fixed. Creation date parsing for contacts was fixed; correct timestamps will now be returned, rather than unformatted ones - if your application relies on the broken variant, you'll need to change your code. Some additional parameters were added to the `net` and `parse` methods to facilitate NIC handle lookups; the defaults are backwards-compatible, and these changes should not have any consequences for your code. Thai WHOIS parsing was implemented, but is a little spotty - data may occasionally be incorrectly split up. Please submit a bug report if you run across any issues.
43
51
44
52
*2.2.0 and up*: The internal workings of `get_whois_raw` have been changed, to better facilitate parsing of WHOIS data from registries that may return multiple partial matches for a query, such as `whois.verisign-grs.com`. This change means that, by default, `get_whois_raw` will now strip out the part of such a response that does not pertain directly to the requested domain. If your application requires an unmodified raw WHOIS response and is calling `get_whois_raw` directly, you should use the new `never_cut` parameter to keep pythonwhois from doing this post-processing. As this is a potentially breaking behaviour change, the minor version has been bumped.
@@ -51,6 +59,23 @@ The manual (including install instructions) can be found in the doc/ directory.
51
59
52
60
If any of those apply, don't hesitate to file an issue! The goal is 100% coverage, and we need your feedback to reach that goal.
53
61
62
+
## License
63
+
64
+
This library may be used under the WTFPL - or, if you take issue with that, consider it to be under the CC0.
65
+
66
+
## Data sources
67
+
68
+
This library uses a number of third-party datasets for normalization:
Be aware that the OpenFlights database in particular has potential licensing consequences; if you do not wish to be bound by these potential consequences, you may simply delete the `airports.dat` file from your distribution. `pythonwhois` will assume there is no database available, and will not perform airport code conversion (but still function correctly otherwise). This also applies to other included datasets.
78
+
54
79
## Contributing
55
80
56
81
Feel free to fork and submit pull requests (to the `develop` branch)! If you change any parsing or normalization logic, ensure to run the full test suite before opening a pull request. Instructions for that are below.
0 commit comments