GF
{first_name = message.from_user.first_name} типо так
Size: a a a
2020 August 28
W
{first_name = message.from_user.first_name} типо так
{first_name = message.from_user.first_name + ' ' + message.from_user.last_name if message.from_user.first_name and message.from_user.last_name else 'у вас не указаны фамилия или имя, пожалуйста укажите и только потом продолжайте пользоваться этим ботом' }
W
лучше так
W
Ты про pep8 забыл
Я пофиксил, не благодари
Я пофиксил, не благодари
𝕡
{first_name = message.from_user.first_name + ' ' + message.from_user.last_name if message.from_user.first_name and message.from_user.last_name else 'у вас не указаны фамилия или имя, пожалуйста укажите и только потом продолжайте пользоваться этим ботом' }
А если просто здравствуйте и first name?
W
Language:
Source:
Result:
py3
Source:
import this
Result:
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
W
{first_name = message.from_user.first_name} типо так
таким образом не ок
W
first_name = message.from_user.first_nameесли до этого указать, то ок
W
а ещё лучше - распарсить в отдельном классе
GF
а ещё лучше - распарсить в отдельном классе
Что?
𝕡
@bot.message_handler(commands=['start'])
def send_start(message):
print(message.chat.id)
bot.send_message(message.chat.id, text='Здравствуйте! ')
И куда его впихнуть
def send_start(message):
print(message.chat.id)
bot.send_message(message.chat.id, text='Здравствуйте! ')
И куда его впихнуть
GF
@bot.message_handler(commands=['start'])
def send_start(message):
bot.send_message(message.chat.id, text=f'Здравствуйте, {message.from_user.first_name}')
W
А как сделать чтоб при старте бота писалось типо здравствуйте и ник твой
text=f' Здравствуйте {first_name} ')
Так не получается
text=f' Здравствуйте {first_name} ')
Так не получается
написать класс, при инициализации объекта которого, из message будут вытягиваться вся необходимая инфа:
class User:Таким образом это:
def __init__(self, message):
self.id = message.from_user.id
self.first_name = message.from_user.first_name
bot.send_message(message.from_user.id, f' Здравствуйте {message.from_user.first_name}')
сократиться до: user = User(message)
bot.send_message(user.id, f' Здравствуйте {user.first_name}')GF
написать класс, при инициализации объекта которого, из message будут вытягиваться вся необходимая инфа:
class User:Таким образом это:
def __init__(self, message):
self.id = message.from_user.id
self.first_name = message.from_user.first_name
bot.send_message(message.from_user.id, f' Здравствуйте {message.from_user.first_name}')
сократиться до: user = User(message)
bot.send_message(user.id, f' Здравствуйте {user.first_name}')И с хуя ли это сокращение?
W
И с хуя ли это сокращение?
Language:
Source:
Result:
py3
Source:
import this
Result:
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
W
Language:
Source:
Result:
py3
Source:
import this
Result:
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
с этого
GF
Language:
Source:
Result:
py3
Source:
import this
Result:
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
Ну да, оно ведь следую зену
GF
Какой-то непонятный User
GF
Который ты должен будешь идти смотреть, что это за херня
GF
Вместо просто прямого обращения