TGTGInsighttelegram intelligenceLIVE / telegram public index
← Python Заметки

TGINSIGHT SIMILAR POSTS

Најди сличен содржај

Изворен канал @pythonotes · Post #242 · 7 мај

Теперь запакуем строку. В этом случае следует передавать тип данных bytes. >>> struct.pack('=s', b'a') b'a' Для записи слова следует указывать количество символов. >>> struct.pack('=5s', b'hello') b'hello' Кстати, запакованный вид соответствует исходному тексту. Всё верно, символ есть в таблице ASCII, то есть его код попадает в диапазон 0-127, он может быть записан одним байтом и имеет визуальное представление. А вот что будет если добавить символ вне ASCII >>> struct.pack(f'=s', b'ё') SyntaxError: bytes can only contain ASCII literal characters. Ошибка возникла еще на этапе создания объекта bytes, который не может содержать такой символ. Поэтому надо кодировать эти байты из строки. >>> enc = 'ёжик'.encode('utf-8') >>> struct.pack(f'={len(enc)}s', enc) b'\xd1\x91\xd0\xb6\xd0\xb8\xd0\xba' Заметьте, длина такой строки в байтах отличается от исходной длины, так как символы вне ASCII записываются двумя байтами и более. Поэтому здесь формат создаём на лету, используя получившуюся длину как каунтер токена. #libs#basic

Hashtags

Резултати

Пронајдени 10 слични објави

Пребарај: #resolved

当前筛选 #resolved清除筛选
Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #220 · 15.01.2020 г., 22:43

A few minutes ago I had a networking issue, making my server unreachable for a bit more than 5 minutes. Got that resolved and the services are responsive again. It may have happen that some messages got processed twice in that unstable period, which is due to how telegram sends updates. I appologize for any inconvenience. The server is now back to operating normal. #resolved

Hashtags

Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #125 · 01.02.2018 г., 17:47

17:46 UTC @BanWarnBot and @RulesRulesBot are back up. 17:50 UTC @HeyAdminBot is back up. 18:00 UTC @moustache_bot is back up. 18:25 UTC finally @StickerTagBot is back up. A file went missing, so not all code to run was there. Basic operation is back. 19:16 UTC @LangInfoBot is back up. 19:26 UTC @BassBoostBot is back up. Lol, as if anyone missed that bot. 19:34 UTC @bonbot is back up soon. Currently fighting with API rate limiting. 19:37 UTC @travis_cibot is back up. 19:45 UTC and the health checks are all good now. #resolved#update

Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #278 · 27.03.2021 г., 16:48

The worker node of @JoinCaptchaBot just restarted ungreacefully, in some cases causing up to 6 times the same messages. The good news is, while it happend multiple times in the same second, any missed out kicks were now processed as well (6 times). The issue has been identified and will be resolved soon. Sorry for your inconvinience. #resolved#JoinCaptchaBot

Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #252 · 04.07.2020 г., 15:57

@BanWarnBot is nowsuccessfully back up and running the newest version: Here's a list of what's new: New /kick and /ban commands: Just like the /warn one, but immediately removes the user from the chat, either once or permanently. You can specify a reason for why you kicked/banned someone after the command. Those kicks count into the normal warn count, because they are kinda like special warns. Those 3 commands, /warn, /kick and /ban now also allow the first thing after the command to be the id of a user, in the format of #1234, or a user mention. This can come in handy if you don't have a message to reply to. Overhaul of the warning lists: Now the list of /listwarnings and /listallwarnings will link you to the message warn message, if you press the date stamp. Also support for distinguishing automatic kicks/bans and manual kicks/bans has been added. #update#BanWarnBot#resolved

Luckydonalds Bots: Development/Status

@luckydonaldsbots · Post #218 · 08.09.2019 г., 19:48

Updated @HeyAdminBot: - Improved handling of private groups, will now export the join link if the bot has the rights for that - Added a direct link to the message ("requested") - Randomizing order of admins called so it's not always the same one being the first to respond. - Fixed bug where the first admin would receive the messages meant for the other admins as well. #update#resolved#HeyAdminBot