Ранее я делал серию постов про битовые операторы.
Вот вам ещё один наглядный пример как это используется в Python в модуле re.
Чтобы указать флаг для компилятора нам надо указать его после передаваемой строки. Например, добавляем флаг для игнорирования переноса строки.
pattern = re.compile(r"(\w+)+")
words = pattern.search(text, re.DOTALL)
А как указать несколько флагов? Ведь явно будут ситуации когда нам потребуется больше одного. Кто читал посты по битовые операторы уже понял как.
pattern.search(text, re.DOTALL | re.VERBOSE)
А теперь смотрим исходники, что находится в этих атрибутах?
Не удивительно, степени двойки. Почему? Потому что каждое следующее значение это сдвиг единицы влево.
>>> for n in [1, 2, 4, 8, 16, 32, 64, 128, 256]:
>>>
print(bin(n))
0b1
0b10
0b100
0b1000
0b10000
0b100000
0b1000000
0b10000000
0b100000000
Чтобы было понятней, давайте напишем тоже самое но иначе, добавим ведущие нули:
000000001
000000010
000000100
000001000
000010000
000100000
001000000
010000000
100000000
Не понятно что тут происходит? Читай три поста про битовые операторы начиная с этого ➡️https://t.me/pythonotes/45
В общем, это пример применения побитовых операций в самом Python.
Теперь вы знаете Python еще немного лучше)
#tricks#regex#libs
Updated @RulesRulesBot:
Bringing you some much requested features:
- It is now possible to get the last set rules or welcome text with /getgreeting and /getrules. That way you don't have to recreate all the HTML formatting, but can copy, paste and edit.
- It will delete old messages (greetings and rules) after more than 5 minutes. Not always exactly 5 minutes, as the cleanup job might not run every minute.
- If you grant admin rights to delete messages to the bot, it will also clean up any /rules and /greet command messages when deleting the sent message that.
#update#RulesRulesBot
Updated@RulesRulesBot:
Will now check for syntax error regarding variable usage when you set new rules or greeting text.
If you have an error there, it is most likely because you wanted to use "{" or "}" in your text. It will now tell you that you can use {{ or }} to display those.
Note that HTML errors where Telegram doesn't accept the message still can't be checked as the bot doesn't send the text immediately.
#update#RulesRulesBot
Updated @BanWarnBot, added {user_id}, {user_url} and {user_link} variables. This way you can link the user. This is also the new default replacing the bold text, in case you did't set any greeting.
#RulesRulesBot#update
New beta feature for @RulesRulesBot:
Read-the-Rules Highscores.
When enabled with /enable_highscores@RulesRulesBot,
the bot will send a game message to your chat which allows the bot to send highscores if somebody reads the rules, who hasn't before or hasn't after a change in the rules.
This might engage reading the rules more, and provide an overview for admins if joined users clicked the rules links.
If you don't like it, just send /disable_highscores@RulesRulesBot, and delete the game message.
Note, the game message is needed for telegram to notify about changed highscores. If the message got accidentially deleted, it can be recreated with /enable_highscore@RulesRulesBot command, which will also restore the scores.
Screenshot: https://t.me/luckydonaldsbots/146
#RulesRulesBot#beta#update
It was brought to attention that with some bots admin commands were no longer working.
That was happining for the bots migrated yesterday, because of the new bot API version.
This is #fixed now.
Thanks for letting me know, A. A.!
#BanWarnBot#RulesRulesBot#JoinCaptchaBot
I will soon migrage some services onto a new server.
Therefore those services will be unavailable for the next two hours:
@JoinCaptchaBot@BanWarnBot@RulesRulesBot and @ForwardWhitelistBot.
#downtime
#JoinCaptchaBot#BanWarnBot#RulesRulesBot#ForwardWhitelistBot
I will definitely work hard to keep the most important group management services stable, including:
@JoinCaptchaBot, @RulesRulesBot, @BanWarnBot, and @HeyAdminBot. And for now also the less important @NoServiceBot.
#PermalinkBot#NoServiceBot#RulesRulesBot, #BanWarnBot#HeyAdminBot
#ongoing#issue