sopel-iplookup
Sopel plugin .ip command:
16:22 <SnoopJ> !ip 8.8.8.8 16:22 <testibot> [IP/Host Lookup] Downloading GeoIP database, please wait... 16:22 <testibot> [IP/Host Lookup] Hostname: dns.google | Location: United States | ISP: AS15169 GOOGLE
Install
The recommended way to install this plugin is to use pip:
$ pip install sopel-iplookup
Note that this plugin requires Python 3.7+ and Sopel 7.1+. It won’t work on Python versions that are not supported by the version of Sopel you are using.
Configure
sopel-iplookup can be configured by invoking Sopel’s interactive wizard:
$ sopel-plugins configure iplookup Configure Sopel GeoIP Lookup Plugin Please consult sopel-iplookup's README to learn about its settings. Path to existing GeoIP db files (leave empty to auto download): MaxMind license key (optional): (hidden input)
By default, sopel-iplookup will look in a few standard locations for GeoIP database files. If it can’t find existing database files, it will download them from an automated mirror on GitHub.
You can optionally provide your own MaxMind license key, and the plugin will download directly from them instead. Alternatively, if your OS distribution already has GeoIP database files kept up-to-date by the system package manager, you can provide the path where those files are stored.
Notes
This plugin replaces a built-in Sopel plugin formerly called ip, you may need to update your bot configuration to replace ip with iplookup if you are e.g. excluding this plugin.
Changelog
1.1.0
- plugin, config: add config field for MaxMind license key (#4, #5)
If no MaxMind key is provided, the plugin will download from a mirror of the .mmdb files on GitHub. With a license key, the plugin downloads directly from MaxMind.
plugin: slightly better logging during/after DB downloads
meta: add automated release workflow using PyPI Trusted Publishing (#7)
1.0.0
Initial release. Replaces ip plugin formerly shipped as part of sopel.
Metadata
Release files for sopel-iplookup 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sopel_iplookup-1.1.0.tar.gz | 6.8 kB | Without provenance | Details for sopel_iplookup-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sopel_iplookup-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for sopel_iplookup-1.1.0-py3-none-any.whl |
Total release size: 14.3 kB
Release files / sopel_iplookup-1.1.0.tar.gz
| Download URL | sopel_iplookup-1.1.0.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3386999bb131d0d507e70151503a644a20ed658accb221c13c06b69f6865c8d
|
|
BLAKE2b-256 checksum How to use checksums |
40d4515fe802850bf219e0952817ece3ae3fa9b7b3c69b324afd611869a1a062
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Release files / sopel_iplookup-1.1.0-py3-none-any.whl
| Download URL | sopel_iplookup-1.1.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ade6974c15aa895e849353e8a05fded2ec054caae462c15d43ead11ea5d33c9d
|
|
BLAKE2b-256 checksum How to use checksums |
036cb5729eb97578364cecbec1e36d9d2a4f6f635de240ec137195b5ce4837a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Security for sopel-iplookup 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.