pyth | Python text markup and conversion | Document Editor library

You can give pygrabber a shot. "# This code lists the cameras connected to your PC:" (source)

After much trial and error I think I have a solution to the problem. I tried registering a cleanup function with the tp_finalize slot of PyThing but this didn't quite work. It seems that functions registered to weakref's finalize method take priority in terms of deallocation order on exit. Because Context is using weakref's finalize it gets cleaned up before PyThing on exit. I needed to register PyThing with weakref in order to get the correct deallocation order. PyThing 's deallocation method works as normal (i.e. it performs both a ref count decrement on the owned context as well as deallocates C_CLASS) but I also created a separate method to register PyThing with weakref (done within PyThing's init method in the C api) that only deallocates the C_CLASS. If the ref count gets to 0 in the middle of the program the deallocation method gets called as it should, however on exit the finalize method gets called and destroys the C_CLASS before the context is destroyed (the deallocation method may still be called so C_CLASS should be checked if it is NULL so delete/free isn't called a second time).

I think the append append() method won't be called inside python.

It's been called inside the compiler implicitly:

which indicates to me that the variable n is somehow transformed from an Int to a Float at some point during the list comprehension.

Quite the opposite. You've declared n to be an Int in the type signature, and that fixes it forever. The Float here is hyp x y. You're asking whether hyp x y is an element of [1..n]. elem :: a -> [a] -> Bool, so it only makes sense to ask that question when you have an object that's the same type as the list's elements. That's the mismatch: to use elem with a Float and a list, you need that list to be a [Float]. But since the list is [1..n], it's clearly a [Int].

As for what you should do differently, I would suggest not using any floating-point arithmetic at all for this function. Probably it's fine for the scales you're working at, but I'd be too worried about rounding errors giving me wrong answers. Instead of searching for pairs such that sqrt (a^2 + b^2) is an integer, which requires a sqrt, you can search for triples such that a^2 + b^2 == c^2.

You can use regular expression:

It sounds like you're confusing modules you install on the machine running Visual Studio Code and modules you install in Micropython on the ESP32.

They're totally separate.

Python on your Windows machine can use venv.

MicroPython doesn't use venv at all (there apparently is a clone of venv for MicroPython but it's not readily apparent what it does or why or how you'd use it). It is a completely separate instance of Python from the one on your Windows machine, and it doesn't operate the same way. Modules you install under venv won't be visible or usable by MicroPython. Numpy in particular is not available for MicroPython.

Many modules need to be written specially to work with MicroPython. MicroPython isn't running in a powerful operating system like Windows, MacOS or Linux. It's running in a highly constrained environment that lacks much of the functionality of those operating systems, and that has extremely little memory and storage compared to them. You can't expect that a module written for regular Python will just work on MicroPython (and likewise, many MicroPython modules use hardware features like I2C or SPI access that may not be available on more powerful, general purpose computers).

Only modules available with upip will be available for MicroPython. They'll need to be installed in the instance of MicroPython running on the ESP32, not in the instance of Python running under Windows. They're two, totally separate instances of Python.

You were very close, but needed to use the reversed keyword on word:

Yes I wanted to thank everyone for their help. While I have a time lime for my project I will dit the post to see my work around as well. Thanks.

When you create the client are you specifying the correct tld parameter for the exchange you use?

If you want to interact with the main exchange, then no tld parameter is required and it defaults to com