magica | easy setup , high level API | Runtime Evironment library

I had this issue earlier and fixed it with listener.subscribe:

Call BotWait without using await. When BotWait finishes, have it send a proactive message.

Just to clarify your confusion, here is the updated function:-

To hide button b1 displayed by pack manager, use b1.pack_forget(). To display it again, you can do it the same way as if it was never displayed before: using b1.pack(), b1.place() or (if nothing else is packed already on screen) b1.grid().

Notice that b1 will be packed at the bottom (after all other already packed widgets). To avoid that, I suggest using different layout manager (grid or place) or, when you want to show b1 again, hide all the widgets that should be below b1 and then pack b1 and them in right order.

I wasn't able to run your code properly because of missing functions, so I can't tell if something is wrong there and debug it for you.

Since you're novice, I'd like to suggest you two tkinter reference sites to find answers to your questions more easily and to expand your knowledge of tkinter: effbot.org & infohost.nmt.edu

There you can find out how gridding works in detail. In short, grid has rows and columns. When being gridded, each widget is placed in its own cell (i-th row, j-th column). By default, each row/column is as tall/wide as the tallest/widest widget inside. That means, if there aren't any widgets in certain row/column, that row/column is not displayed. Of course, you can tweak that with grid options (e.g. row_configure() might help there) For further info check out the sites I linked.

Since the target text is, according the HTML snippet posted above, the only direct child text node from post_body that is not blank or whitespace, you should be able use the following XPath expression to get that text:

You are right that abbreviating a constant or aliasing a function is perfectly fine. But then, hints are not warnings, but merely comments about your program that may or may not tell you something you didn't know yet.

Hence the notion of "hint against" is mistaken. Nor should you strive to make your code "hints free".

Ironically, it looks like the hint in question would need another hint to explain it. It should read:

I, the compiler, use to move type annotated constants like your 'name' to the top level, because it is safe to do so and may eliminate some or all nested levels of let. This will also speed up things later in type checking, code generation and run time. In addition, you might consider to do the same yourself, lest you end up defining the same constant over and over in different let expressions or where clauses.

Please note that, in

try this out. Hope this work as you expected

Before this line:

In Python 3 your original string is a Unicode string, but contains Unicode code points that look like UTF-8, but decoded incorrectly. To fix it: