PythonSimpleBlogger library (simple_blogger)
This is simple library to make simple blog project with Python. The library is distributed under the MIT license and can be downloaded and used by anyone.
How to install
To install, you can use the command:
pip3 install simple_blogger
Or download the repository from GitHub
Initialization
Just start with a simple code.
blogger = simple_blogger.CommonBlogger(PUT-YOUR-TELEGRAM-PRIVATE-CHAT-ID-IN-HERE)
blogger.init_project()
It initalizes folder structure of your own blog project in the working directory.
Blog topics
Find project ideas json-file in files/ideas folder. Fill it with topics and categories of your blog.
Creating tasks
Call push.
blogger.push()
It creates tasks json-file in files folder with dates of publications and prompts to AI that generate image and text for topics.
Adding Tasks
Put any json-file in files/ideas folder. It has to be idea-structured. You can put as many idea-files in idea folder as you want.
Call revert to put unhandled tasks back in backlog.
blogger.revert()
Call push again. Now all backloged tasks and new ideas are in progress.
Publication Review
Call review to send tommorow's publication to your private telegram channel.
blogger.review()
Publication
Call send to send today's publication to your public telegram channel.
blogger.send()
Note: call review before send or call send with image_gen=True(to produce image) and text_gen=True(to produce text).
Error handling
If something goes wrong method sends Exception text to your private telegram channel.
Default parameters
Library uses working directory name as project name and production telegram channel name by default.
Environment variables
Library uses dall-e-3 model to generate images and deepseek-chat to generate texts by default and sends publications to telegram channels.
It needs following environment variables:
- BLOGGER_BOT_TOKEN
- OPENAI_API_KEY
- DEEPSEEK_API_KEY
Yandex generators needs following environment variables:
- YC_API_KEY
- YC_FOLDER_ID
From the developer
There are(or will be) more examples of using this library in sibling repos on GitHub
Metadata
Release files for simple-blogger 0.2.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| simple_blogger-0.2.15.tar.gz | 18.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| simple_blogger-0.2.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.3 kB
Release files / simple_blogger-0.2.15.tar.gz
| Download URL | simple_blogger-0.2.15.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b402e7936178b621aaf8c6669007ccc0a47621668220110c8ab120dec084f495
|
|
BLAKE2b-256 checksum How to use checksums |
f03752e96e91ed17334851cca9e69bb12d5c1b7dfbe6d4f5bf6270d395cfb78e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 20, 2026.
Transparency logRelease files / simple_blogger-0.2.15-py3-none-any.whl
| Download URL | simple_blogger-0.2.15-py3-none-any.whl |
|---|---|
| Size | 30.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df78880afb702627ad0f4334d489caad70bce8ef7a90b5e82da9aa1cb8be8b40
|
|
BLAKE2b-256 checksum How to use checksums |
3be36db0553aebffc0c9c4d0f89cfe833db5d974f0ed6b2bc6ea975263c4ed3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 20, 2026.
Transparency log