mlseo
Pythonic SEO in JupyterLab
Install
pip install mlseo --upgrade
How to use
Start a new Notebook, preferably in standalone JupyterLab. Then type:
from mlseo import *
Welcome to _ (\ To chase the rabbit,
_ __ ___ | |___ ___ ___ \\_ _/(\ run: look()
| '_ ` _ \| / __|/ _ \/ _ \ 0 0 _\)___
| | | | | | \__ \ __/ (_) | =(_T_)= )*
|_| |_| |_|_|___/\___|\___/ /"/ ( /
The adventure begins! <_<_/-<__|
The Most Important Things
Storing API Responses into Database
This package contains a variety of building-blocks for constructing "deliverables" for the field of Search Engine Optimization (SEO). The goal is to make expressing such deliverables "light and breezy" by establishing certain conventions. For example, to crawl 1-page of a site into a local database:
import httpx
from sqlitedict import SqliteDict as sqldict
url = 'https://mikelev.in/'
with sqldict('crawl.db') as db:
db[url] = httpx.get(url)
db.commit()
Using Tuples As Composite-Keys
We are using SQlite as a key-value database in a way that requires the keys to be strings. Keys must be unique so if we use the URL as the key we can store each page we crawl only once. Instead of just a URL, the key to your database can contain a URL and Date so that we can crawl sites on subsequent days and store it into the same key-value database. Such a tuple key looks like this:
from datetime import date
url = 'https://mikelev.in/'
atuple = (date.today(), url)
Pickling and Unpickling
Tuples must become strings to be a key in the key-value database we're using. This is accomplished through pickling. We "pickle" the tuple to make it a string, then can use that string as a key in the dictionary database.
import pickle
from datetime import date
pkl = lambda x: pickle.dumps(x)
unpkl = lambda x: pickle.loads(x)
url = 'https://mikelev.in/'
today = date.today()
atuple = (today, url)
now_a_string = pkl(atuple)
print(now_a_string)
Pickling Keys For Database
This example uses a pickled tuple containing the Date and the URL as the database key. It shows data both going in and coming out of the database. Notice the pickled key is restored to its original form. This approach prevents duplicate records in your database. Because dictionary keys must be unique, attempts to insert a new record with the same URL+Date key will fail, meaning this crawler can only record each page on the site once per day.
import httpx
import pickle
from datetime import date
from sqlitedict import SqliteDict as sqldict
pkl = lambda x: pickle.dumps(x)
unpkl = lambda x: pickle.loads(x)
url = 'https://mikelev.in/'
# Data goes in
with sqldict('crawl.db') as db:
tupkey = (date.today(), url)
db[pkl(tupkey)] = httpx.get(url)
db.commit()
# Data comes out
with sqldict('crawl.db') as db:
for tupkey in db:
adate, url = unpkl(tupkey)
print(adate, url)
mlseo Tutorials
HOUSEKEEPING: Once you have the basic trick of using a persistent dictionary and using tuples as your primary key, you'll need a place to put the database and all your other INPUT/OUTPUT files besides lumping it all into the top-level of your folder.
A Word About JupyterLab
Recovering pip installs
For now standalone Jupyter has to be reinstalled a lot and its easy to lose your pip-installed packages. For mlseo you can get all the necessary packages back by just typing this into a Code cell:
pip install mlseo --upgrade
Useful Dev Tools
I also recommend installing nbdev and nb_black if you're doing any development work inside Jupyter:
pip install nb_black
pip install nbdev
Restart Kernel & Clear All Outputs A LOT
And lastly, shortcuts always get deleted between Jupyter reinstalls so here's my most important shortcut. It's always a good time to Restart kernel and clear all outputs.
{
"shortcuts": [
{
"command": "kernelmenu:restart-and-clear",
"keys": [
"Ctrl Shift R"
],
"selector": "body"
}
]
}
Metadata
Release files for mlseo 0.0.22
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 |
|---|---|---|---|---|
| mlseo-0.0.22.tar.gz | 20.8 kB | Without provenance | Details for mlseo-0.0.22.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mlseo-0.0.22-py3-none-any.whl | Python 3 | none | any | Details for mlseo-0.0.22-py3-none-any.whl |
Total release size: 39.8 kB
Release files / mlseo-0.0.22.tar.gz
| Download URL | mlseo-0.0.22.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6047d2211cf86b710165f4b1a141b3e3bc63425efb2e71994b35842d309ca503
|
|
BLAKE2b-256 checksum How to use checksums |
bde37720eca2f4841d89994bc7350cda097bdb685ce2e47fe527766d6b48885b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.3
|
Release files / mlseo-0.0.22-py3-none-any.whl
| Download URL | mlseo-0.0.22-py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
316cba83c02b3be6a9668122f7d8ea5e8320ed4436288f9219cfdd4d9839b8a5
|
|
BLAKE2b-256 checksum How to use checksums |
6f2dba18905b6f729f98b09865430b3a7fd887eac613a10fa067422c9825b065
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.3
|
Security for mlseo 0.0.22
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.