fix: correct f-string typo in README debug print and update run instructions
- Fix incorrect f-string prefix 'f{' to '{' in README example bot's on_message debug print
- Replace hardcoded 'python bot.py' with generic '[your-script].py' placeholder in run instructions
- Remove license field from pyproject.toml metadata configuration
This commit is contained in:
parent
3628ab98f5
commit
3b5cb74d94
@ -63,7 +63,7 @@ class ExampleBot(Bot):
|
|||||||
await self.send_message(data.channel_uid, result)
|
await self.send_message(data.channel_uid, result)
|
||||||
|
|
||||||
async def on_message(self, data):
|
async def on_message(self, data):
|
||||||
print(f"Message from f{data.user_nick}: {data.message}")
|
print(f"Message from {data.user_nick}: {data.message}")
|
||||||
|
|
||||||
message = data.message.lower()
|
message = data.message.lower()
|
||||||
result = None
|
result = None
|
||||||
@ -84,6 +84,6 @@ asyncio.run(bot.run())
|
|||||||
#### Run the bot
|
#### Run the bot
|
||||||
Make sure you have (still) activated your virtual env.
|
Make sure you have (still) activated your virtual env.
|
||||||
```bash
|
```bash
|
||||||
python bot.py
|
python [your-script].py
|
||||||
```
|
```
|
||||||
If you get the error 'python not found' or 'aiohttp not found', run `source .venv/bin/activate` again and run `python bot.py` again.
|
If you get the error 'python not found' or 'aiohttp not found', run `source .venv/bin/activate` again and run `python [your script].py` again.
|
||||||
|
|||||||
@ -6,7 +6,6 @@ build-backend = "setuptools.build_meta"
|
|||||||
name = "snekbot"
|
name = "snekbot"
|
||||||
version = "1.0.0"
|
version = "1.0.0"
|
||||||
readme = "README.md"
|
readme = "README.md"
|
||||||
license = { file = "LICENSE", content-type="text/markdown" }
|
|
||||||
description = "Bot API for Snek chat"
|
description = "Bot API for Snek chat"
|
||||||
authors = [
|
authors = [
|
||||||
{ name = "retoor", email = "retoor@molodetz.nl" }
|
{ name = "retoor", email = "retoor@molodetz.nl" }
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user