On Tue, 22 Mar 2022 at 10:52, Skip Montanaro wrote:
>
> Given that both asyncio & tkinter are modules in the standard lib and both
> have event loops, I would have expected to find some "best practice"
> solution to mixing the two. I've not used asyncio, but might find it useful
> with the pynput
Given that both asyncio & tkinter are modules in the standard lib and both
have event loops, I would have expected to find some "best practice"
solution to mixing the two. I've not used asyncio, but might find it useful
with the pynput module in the context of a Tk app. I see a few solutions
out in
On 22/03/2022 10.17, Chris Angelico wrote:
> On Tue, 22 Mar 2022 at 08:13, Paul St George wrote:
>>
>>
>> When I am writing code, I often do things like this:
>>
>> context = bpy.context # convenience
>>
>> then whenever I need bpy.context, I only need to write context
>>
>>
>> Here’s my question
On 21Mar2022 22:12, Paul St George wrote:
>When I am writing code, I often do things like this:
>
>context = bpy.context # convenience
>
>then whenever I need bpy.context, I only need to write context
>
>
>Here’s my question:
>
>When I forget to use the convenient shorter form
>
>why is bpy.conte
Chris,
I think you understood the context but not the premise in a sense that wasin
the way Paul was thinking. His premise is way off
He seems to be thinking of something like a macro concept as iscommonly used in
languages like C so:
#define context bpy.context
That could, in such languages, use
No, nor did I suggest that you did. `context` is presumably an
attribute in the `bpy` module, for which you are creating a `context`
attribute in your module.
On Mon, 2022-03-21 at 22:31 +0100, Paul St George wrote:
> Hi,
> I do not (knowingly) have a module called ‘context'.
>
>
>
>
> > On 21
Hi,
I do not (knowingly) have a module called ‘context'.
> On 21 Mar 2022, at 22:24, Paul Bryan wrote:
>
> Assuming `bpy` is a module, you're creating a new attribute in your module,
> `context`, that contains a reference to the same object that is referenced in
> the `context` attribute in
Assuming `bpy` is a module, you're creating a new attribute in your
module, `context`, that contains a reference to the same object that is
referenced in the `context` attribute in the `bpy` module.
On Mon, 2022-03-21 at 22:12 +0100, Paul St George wrote:
>
> When I am writing code, I often do th
On Tue, 22 Mar 2022 at 08:13, Paul St George wrote:
>
>
> When I am writing code, I often do things like this:
>
> context = bpy.context # convenience
>
> then whenever I need bpy.context, I only need to write context
>
>
> Here’s my question:
>
> When I forget to use the convenient shorter form
When I am writing code, I often do things like this:
context = bpy.context # convenience
then whenever I need bpy.context, I only need to write context
Here’s my question:
When I forget to use the convenient shorter form
why is bpy.context not interpreted as bpy.bpy.context?
—
Paul St Ge
On Mon, 21 Mar 2022 15:36:50 + (UTC), "Kevin M. Wilson"
declaimed the following:
>The use of Java options environment variables detected.
>Such variables override IDE configuration files (*.vmoptions) and may cause
>performance and stability issues.
>Please consider deleting these variables
Greetings Python coders,
I have installed the Pycharm IDE, and upon successfully auto
install of the path/environment statements.
The IDE opened and displayed (bottom right corner):
The use of Java options environment variables detected.
Such variables override IDE configuration files
Am 19.03.22 um 01:08 schrieb Ankit Agarwal:
This is a very specific question. I am trying to figure out whether or not
I can use pre-built python libraries and headers on Windows in a MinGW
build on Linux.
With the mingw cross-compiler on Linux that should be possible, however
I guess it might
13 matches
Mail list logo
