PythonQt Activity
Dynamic Python binding for Qt Applications
Brought to you by:
florianlink,
marcusbarann
Activity for PythonQt
-
Miguel Angel posted a comment on discussion Help
Hi, sorry for asking as the question may be stupid, but I did not find any information around. Is there any support available or planned for Qt 6.2? thanks in advance!
-
foghua posted a comment on discussion Help
Suppose there is a QByteArray object transfered from cpp to python script, how can I read it's data to a python list object? Use while loop to read data byte by byte? Any elegant solution?
-
Suppose there is a QByteArray object transfered from cpp to python script, how can I read it's data to a python list object? Use while loop to read data byte by byte? Any elegant solution?
-
you need use a python string as the input parameter
-
Flower lady modified a comment on discussion Help
I've done a bit of digging, and noticed that PythonQt simply isn't initializing at all, which is upsetting. I'm reexamining my library paths and seeing if there's a way to figure this out. Edit: I was wrong, PythonQt::self() looks fine, at least from what I can tell. It exists at least. Edit 2: It looks like I'm not getting any errors on PythonQt::init(), and Py_Initialize() is getting called from PythonQt. However, Py_IsInitialized() returns false after initializing PythonQt, which I guess means...
-
I've done a bit of digging, and noticed that PythonQt simply isn't initializing at all, which is upsetting. I'm reexamining my library paths and seeing if there's a way to figure this out. Edit: I was wrong, PythonQt::self() looks fine, at least from what I can tell. It exists at least. Edit 2: It looks like I'm not getting any errors on PythonQt::init(), and Py_Initialize() is getting called from PythonQt. However, Py_IsInitialized() returns false after initializing PythonQt, which I guess means...
-
I've done a bit of digging, and noticed that PythonQt simply isn't initializing at all, which is upsetting. I'm reexamining my library paths and seeing if there's a way to figure this out.
-
So, I will say that I have PythonQt working beautifully with a qmake build. However, times are changing, and so must I. I've ported pretty much everything over into CMake. However, Python is the one thing that is not working quite right. As I said, I'm getting the ModuleNotFoundError: No module named \PythonQt\. So, something is not quite right. I would very much appreciate help in either 1) figuring out what is wrong with my cmake, or 2) figuring out where PythonQt actually defines itself on the...
-
I ask because I am trying to get a slot working for getitem, but no dice for me, so I might be using the wrong types. I attempted with : public slots: ... double __getitem__(MyVectorType* v, int idx) const;
-
Wonderful, thanks Florian! Any tips on where to go to look up these sorts of things? The documentation is a bit sparse. I can also dig into the code, but there is a LOT of code, and it's hard to tell where the meat of the C++ to Python conversion is happening.
-
Florian Link posted a comment on discussion Help
I think you need a negate slot and the type enum is Negate. On Mon 16. Nov 2020 at 02:24, Flower lady fancyflowerlady@users.sourceforge.net wrote: Hey folks, is there a way to support negation for my custom types, e.g., something = -my_type_instance? I have in-place subtraction implemented using the correct flags and overriding iadd in my C++ wrapper for my class, but it seems like negation is a bit different. Is there support for the negation operator using PythonQt::TypeSlots? Sent from sourceforge.net...
-
I looked this up, you actually need an overloaded __sub__ slot without second object, which returns a negated object. This is due to the code generator and c++, where negation and subtraction is the same -operator
-
Hey folks, is there a way to support negation for my custom types, e.g., something = -my_type_instance? I have in-place subtraction implemented using the correct flags and overriding iadd in my C++ wrapper for my class, but it seems like negation is a bit different.
-
KLAI posted a comment on discussion Help
Hi all, I want to add connection type when connecting a signal to slot in python code, I did not find how to do this, can anyone help me please? I've written this code, which work perfectly : from PythonQt import * . . . assert(ui.connect('stop_clicked()',onStopRequest)) ui is a wrapped object. Thank you in advance.
-
Hi all, I'm developping a Qt application that uses PythonQt. I'm running this code in Qthread : PythonQt::init(PythonQt::IgnoreSiteModule | PythonQt::RedirectStdOut); PythonQtObjectPtr m_mainContext = PythonQt::self()->getMainModule(); m_mainContext.evalScript(script_python); When I stop the thread, it's not stopped immediatly, it wait for the evalscript to finish, and then the thread stopped. I want to know, how to make it stop immediatly, and end the evalscript? Thank you in advance.
-
Hi all, I'm developping a Qt application that uses PythonQt. I'm running this code in Qthread : PythonQt::init(PythonQt::IgnoreSiteModule | PythonQt::RedirectStdOut); PythonQtObjectPtr m_mainContext = PythonQt::self()->getMainModule(); m_mainContext.evalScript(script_python); When I stop the thread, it's not stopped immediatly, it wait for the evalscript to finish, and then the thread stopped. I want to know, how to make it stop immediatly, and end the evalscript? Thank you in advance.
-
Jeffrey Lam posted a comment on discussion Help
Hello PythonQt Team, I am writing to you as I am having issues building PythonQt. A bit of background: I am currently on Python 2.7 (from prebuilt Python installer) as well as Qt 5.12.6 and get the following issue below when running “nmake” in the x86 Native Tools Command Prompt for VS 2019. paraview\PythonQt\src\PythonQtConversion.h(493): error C2664: 'PyObject PyObject_CallMethod(PyObject ,char ,char ,...)': cannot convert argument 2 from 'const char [6]' to 'char *' followed by: Generating Code......
-
Got it, thanks again Florian. Turns out, I had introduced a stray _DEBUG definition in PythonQtPythonInclude, which was ruining everything. So as I'd suspected all along, it was my fault. I'd added that line a year ago to test something and had forgotten about it. As to why I hadn't caught it when I reinstalled PythonQt, it turns out git also wasn't tracking my changes properly, so things didn't actually get overwritten when I pulled from the repo. An unfortunate comedy of errors.
-
Hi Florian, Unfortunately, I tried all of that, and still no luck. I've even gone as far as to pull PythonQt's source directly into my own project, and I'm STILL getting the error in release build: Error LNK2038 mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in com_trolltech_qt_core_builtin0.obj grand_blue C:\Users\dante\Documents\Projects\grand-blue-engine\grand_blue\PhysXCommon_static_32.lib(GuFeatureCode.obj) 1 Error LNK2038 mismatch detected for 'RuntimeLibrary':...
-
Maybe qmake does not generate correct release vcxproj files for you. You could try to change the pro file to build release only. Google the qmake docs how to configure release only in a pro file. (It was like this years ago, but nowadays I thought release and debug vcxproj settings would be ok). On Fri 12. Jun 2020 at 08:56, Florian Link florianlink@users.sourceforge.net wrote: Yes, the moc required and it only generates addition cpp files that are compiled like the rest of the files. Hm, I would...
-
Yes, the moc required and it only generates addition cpp files that are compiled like the rest of the files. Hm, I would try to setup my installation anew, remove all tmp files, recreated vcxproj and so on, like you start on a clean machine. On Thu 11. Jun 2020 at 22:55, Flower lady fancyflowerlady@users.sourceforge.net wrote: Hi Florian, glad to hear from you! Unfortunate that you haven't run into this issue. I actually hadn't made any modifications to the MSVC solution before things stopped working....
-
Sorry but I really don’t know. On Thu 11. Jun 2020 at 21:04, Flower lady fancyflowerlady@users.sourceforge.net wrote: @florianlink, are you okay? You are my shining light. Release build not working Sent from sourceforge.net because you indicated interest in < https://sourceforge.net/p/pythonqt/discussion/631393/> To unsubscribe from further messages, please visit < https://sourceforge.net/auth/subscriptions/>
-
Hi Florian, glad to hear from you! Unfortunate that you haven't run into this issue. I actually hadn't made any modifications to the MSVC solution before things stopped working. I just have been building in debug for the past few months, and finally made the leap to compile a release version of the DLLs. I'm about 80% convinced that this is a very strange problem with MOC. I'm using QT 5.12, and I'm not sure if there are any oddities that have been introduced. Which leads me to the question, is it...
-
I mean I never had that problem before and have no idea why it happens for you. What was your last change before it stopped working? On Thu 11. Jun 2020 at 21:04, Flower lady fancyflowerlady@users.sourceforge.net wrote: @florianlink, are you okay? You are my shining light. Release build not working Sent from sourceforge.net because you indicated interest in < https://sourceforge.net/p/pythonqt/discussion/631393/> To unsubscribe from further messages, please visit < https://sourceforge.net/auth/s...
-
@florianlink, are you okay? You are my shining light.
-
Update: Still no luck. I did make another post with more info here: https://github.com/MeVisLab/pythonqt/issues/11 It seems that maybe, even in release mode, the MDd_DynamicDebug runtime library is being used in stead of MD_DynamicRelease for PythonQt. This doesn't make any sense to me. I've dug through the project settings PythonQt.pro and src.pro, and everything looks fine. All of the settings in my MSVC solution also look fine. The static library itself builds fine for the project PythonQt-Qt5-PythonXY,...
-
Man, tough audience, huh?
-
Hey folks, So, the build process for PythonQt is sort of a black box to me. I've tried to understand it, but there is so much going on here that I've sort of resigned myself to just being happy that my debug build works. However, today that has changed, as I need a release build, and I'm getting an error: LNK2038 mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in com_trolltech_qt_core_builtin0.obj PythonQt-Qt5-Python38 C:\...\PythonQt\src\PythonQtQFileImporter.obj...
-
The problem is QVariant, it can only transport registered meta types. So it can transport a PyObject, a PythonQtObjectPtr and a QObject, but not a custom C++ pointer, it would take it as void* and lose type information. So you either convert it first to something that QVariant will handle, or you register its pointer as a meta type, so that QVariant does not lose the type information. On Thu 5. Mar 2020 at 04:57, Flower lady fancyflowerlady@users.sourceforge.net wrote: Hi Florian, I can confirm that...
-
Hi Florian, I can confirm that the wrapped class gets recognized. What a beautiful thing. Thanks so much!
-
Oh hello Florian! I guess you are the folks. Thanks a bunch for the suggestions, I'll be sure to try them out. Do you think PythonQt would recognize that I've wrapped the C++ class, à la PyCPPWrapperExample? If so, that'd be super swell. Thanks again.
-
I am the 'folks'... Well, this is not a very common use case but there are probably multiple solutions... If your CustomType was derived from QObject, you could just create a Qvariant from that pointer. But since it is a C++ only type, you need to get it through the Qvariant without losing the type information. I think you could register a CustomType POINTER meta type, probably PythonQt would then know the type by the meta type id and since it is a registered C++ class, it should know what to do....
-
Any thoughts on this, folks? I'm tempted to just copy the data from my CustomType into a QJsonObject so I can pass that to Python, but it'd be much cleaner if I could avoid any unnecessary serialization.
-
Long story short, I have a python class TypeProcessor defined such that one of the methods takes a CustomType CPP class. I've wrapped up CustomType as per the PythonQt examples, and am having success simply calling other methods of TypeProcessor via calls to the call routine of the corresponding PythonQtObjectPtr. However, those methods are easy to call since they all take types that cast to QVariants out of the box, so I can do: QVariantList args = QVariantList() << argument; QVariant testOut =...
-
Thanks Florian, can't believe it was as simple as switching the order! I'll look into PythonQtConversion should the need arise, but I think I'm all set!
-
Have you tried changing the order of the slots? The more specific overload needs to come first, I think. But yes, you can do a type check for PythonQt wrappers and get the wrapped ptr from a wrapper. There is no example, but you can see it in PythonQtConversion and PythonQtClassInfo how to do this. On Fri 27. Dec 2019 at 06:02, Flower lady fancyflowerlady@users.sourceforge.net wrote: Hi folks, Does anybody know of a way to obtain a custom type from a PyObject* representing that type, assuming it...
-
I should add that I've tried: MyType* myTypeO = (MyType*)PythonQt::self()->priv()->unwrapForeignWrapper("MyType", o); But unfortunately, this doesn't seem to work, since I don't have a foreign wrapper factory (I'm not even sure what that is). Thanks!
-
Hi folks, Does anybody know of a way to obtain a custom type from a PyObject* representing that type, assuming it is registered with PythonQt and all that? e.g., Can I have the following: MyType* get_object(PyObject* o){ ... } I would like to be able to do this because I can't cleanly overload my function to have something like: MyType* get_object(PyObject* o){ ... Do stuff to o... MyType* myTypeO = toMyType(o); // How can I do this? return myTypeO; } MyType* get_object(MyType* o){ ... Do stuff to...
-
Hi folks, Does anybody know of a way to obtain a custom type from a PyObject* representing that type, assuming it is registered with PythonQt and all that? e.g., Can I have the following: MyType* get_object(PyObject* o){ ... } I would like to be able to do this because I can't cleanly overload my function to have something like: MyType* get_object(PyObject* o){ //... Do stuff to o... MyType* myTypeO = toMyType(o); // How can I do this? return myTypeO; } MyType* get_object(MyType* o){ //... Do stuff...
-
Hi folks, Does anybody know of a way to obtain a custom type from a PyObject* representing that type, assuming it is registered with PythonQt and all that? e.g., Can I have the following: MyType* get_object(PyObject* o){ ... } I would like to be able to do this because I can't cleanly overload my function to have something like: MyType* get_object(PyObject* o){ ... Do stuff to o... MyType* myTypeO = toMyType(o); // How can I do this? return myTypeO; } MyType* get_object(MyType* o){ ... Do stuff to...
-
Hi Florian, sorry, I edited my post quickly but you found it before I did! There was a problem with the metatype registration, as you'd suggested. Thanks!
-
Hm, sounds like the destructor of your wrapper has a problem , at least that is probably what the argument frame deletes on reset... Do you do a qRegisterMetaType in your code? Using just the register macro is not enough... On Thu 19. Dec 2019 at 07:10, Flower lady fancyflowerlady@users.sourceforge.net wrote: Thanks Florian, that's very helpful! I have __iadd__, __isub__, and __imul__ operators working, but I'm getting a heap corruption error when trying to implement __add__, after PythonQtArgumentFrame::reset()....
-
Thanks Florian, that's very helpful! Works like a charm.
-
Thanks Florian, that's very helpful! I have __iadd__, __isub__, and __imul__ operators working, but I'm getting a heap corruption error when trying to implement __add__, after PythonQtArgumentFrame::reset(). Any ideas on what might be causing this? I'm returning a custom type as a value, as such: const Quaternion PyQuaternion::__add__(Quaternion * q, const Quaternion & q2) { return ((*q) + q2); } My custom type is fairly straightforward, class Quaternion: public Serializable { public: Quaternion();...
-
Thanks Florian, that's very helpful! I have __iadd__, __isub__, and __imul__ operators working, but I'm getting a heap corruption error when trying to implement __add__, after PythonQtArgumentFrame::reset(). Any ideas on what might be causing this? I'm returning a custom type as a value, as such: const Quaternion PyQuaternion::__add__(Quaternion * q, const Quaternion & q2) { return ((*q) + q2); } My custom type is fairly straightforward, class Quaternion: public Serializable { public: Quaternion();...
-
Thanks Florian, that's very helpful! I have __iadd__, __isub__, and __imul__ operators working, but I'm getting a heap corruption error when trying to implement __add__, after PythonQtArgumentFrame::reset(). Any ideas on what might be causing this? I'm returning a custom type as a value, as such: const Quaternion PyQuaternion::__add__(Quaternion * q, const Quaternion & q2) { return ((*q) + q2); } My custom type is fairly straightforward, class Quaternion: public Serializable { public: Quaternion();...
-
Yes, there are some default Qt slot names that are looked for, but you have to register that your class supports the feature using an enum in registerCppClass (and you need to use the method on PythonQt::priv(), it has more arguments. Have a look at the generated wrappers, e.g. QPoint to see this in action. Regarding repr, PythonQt always looks for py_toString() slots.
-
Pretty much the title, is there a way to do this? The examples show how to wrap C++ classes with the new_Class and delete_Class syntax as slots, but is it possible to override other python built-in functions?
-
Resolved this, the problem was some incorrect import syntax as I was pulling everything into the main module scope.
-
Okay, I just thought this might be PythonQt-specific, since it runs fine when I run these scripts directly with the same python distribution. Calling the base class directly, as below, also doesn't seem to help me: def update(self, delta_ms: int): """Update routine for TestBehavior""" return BaseBehavior.update(self, delta_ms)
-
Google for super and its problems. Then do direct calls to your base class using BaseClass.xzy(self, arg1, ...). Btw, this has nothing to do with PythonQt itself, it is a pure Python problem.
-
Hi folks, I'm getting a strange bug. I initialize a base class: """ Script for the BaseBehavior class """ from PythonQt.scriptedBehaviors import PythonBehavior # ============================================================================== # Globals # ============================================================================== DEBUG_MODE = True # ============================================================================== # Classes # ==============================================================================...
-
Look for PythonQtRegisterToolClassesTemplateConverterForKnownClass(QDate) and use it with your fully registered class. Your class needs to be copyable by PythonQt, so it needs to be registered as meta type or maybe it is also enough to have a copy constructor on your wrapper, not sure about that. Registering as QMetaType makes sense anyways.
-
Thanks for the prompt response :) I will check that! ty!
-
The easiest way is to use a QList of pointers to YourClass, then you only need to register YourClass with a wrapper/decorator. If you want a QList with YourClass as values, you need to register YourClass as a QMetaType and register a conversion callback for it, have a look how this is done for various list and map types in PythonQt.cpp (there is a macro that registers for vector, QList and QVector with your type). You still need a wrapper/decorator für YourClass for that case. But keep in mind that...
-
Hi, reading the forums I found at the moment QLists of custom objects are not supported, but I need to create one for an specific custom object so when we export it to python it behaves similarly to any of the current lists. Could you please direct us to any example/info or place to see how to do it? I suppose the way to do it may be to write akind of a wrapper to our QList<ourclass> but we are not being successful to do it.</ourclass> Thanks in advance!
-
Okay all, I got this working via: PythonQt::self()->getMainModule().evalScript("test=HelloWorld()"); QVariant instance = PythonQt::self()->getMainModule().getVariable("test"); PythonQtObjectPtr instancePtr = PythonQtConv::QVariantToPyObject(instance); One side problem that I've had was that PythonQt's parseFile() was failing on fflush sporadically. I have no idea why, but I replaced those routines with my own parser, and things are behaving nicely. Thanks!
-
Hello again, I've been thinking about this, and I'm wondering if this object is disappearing because it's not actually getting assigned to an explicit variable with a name? Is there an elegant way of achieving this? I could try by calling PythonQt::self->mainModule()->evalScript(...), but I'm thinking there must be a better way than that. Update: Running: QVariant instance = PythonQt::self()->getMainModule().evalScript("test=HelloWorld()"); Does not work either, I get an invalid QVariant returne...
-
Hello again, I've been thinking about this, and I'm wondering if this object is disappearing because it's not actually getting assigned to an explicit variable with a name? Is there an elegant way of achieving this? I could try by calling PythonQt::self->mainModule()->evalScript(...), but I'm thinking there must be a better way than that. Update: Running: QVariant instance = PythonQt::self()->getMainModule().evalScript("test=HelloWorld()"); Does not work either, I get an invalid QVariant returne...
-
Hello again, I've been thinking about this, and I'm wondering if this object is disappearing because it's not actually getting assigned to an explicit variable with a name? Is there an elegant way of achieving this? I could try by calling PythonQt::self->mainModule()->evalScript(...), but I'm thinking there must be a better way than that.
-
Hi Florian, thanks for the response. I tried what you said, and now my class is simply: class HelloWorld(): def __init__(self): pass def initialize(self): return def update(self): return As before, I am trying to create a class instance via: QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap()); QString type = instance.typeName(); PythonQtObjectPtr instancePtr = PythonQtConv::QVariantToPyObject(instance) The instance I get back doesn't seem to be...
-
Hi Florian, thanks for the response. I tried what you said, and now my class is simply: class HelloWorld(): def __init__(self): pass def initialize(self): return def update(self): return As before, I am trying to create a class instance via: QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap()); QString type = instance.typeName(); PythonQtObjectPtr instancePtr = PythonQtConv::QVariantToPyObject(instance) The instance I get back doesn't seem to be...
-
Hi Florian, thanks for the response. I tried what you said, and now my class is simply: class HelloWorld(): def __init__(self): pass def initialize(self): return def update(self): return As before, I am trying to create a class instance via: ~~~ QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap()); QString type = instance.typeName(); PythonQtObjectPtr instancePtr = PythonQtConv::QVariantToPyObject(instance); ~~~ The instance I get back doesn't seem...
-
Hi Florian, thanks for the response. I tried what you said, and now my class is simply: class HelloWorld(): def __init__(self): pass def initialize(self): return def update(self): return As before, I am trying to create a class instance via: ~~~ QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap()); QString type = instance.typeName(); PythonQtObjectPtr instancePtr = PythonQtConv::QVariantToPyObject(instance); ~~~ The instance I get back doesn't seem...
-
Hi Florian, thanks for the response. I tried what you said, and now my class is simply: class HelloWorld(): def __init__(self): pass def initialize(self): return def update(self): return As before, I am trying to create a class instance via: ~~~ QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap()); QString type = instance.typeName(); PythonQtObjectPtr instancePtr = PythonQtConv::QVariantToPyObject(instance); ~~~ The instance I get back doesn't seem...
-
probably you get a C++ pointer back, because your Python object inherits from a C++ class. I think you should reconsider your design and not derive your Python objects from C++ objects. I would create a Python base class and derive from that. If you want to access C++ parts of your application from it, I would create a Qobject that exposes my application Api and pass it to the constructor of the base class. Deriving from C++ objects in Python only makes sense when having full wrappers with virtual...
-
Hello all, I've been wrestling with this issue for a while, and I'm at my wit's end, so here we go. I'm trying to follow Florian's instructions to instantiate a class, as per this thread from many years ago: https://sourceforge.net/p/pythonqt/discussion/631393/thread/6a851191/. I would then like to call methods of this class. To do this, I am trying to return an instance of the class as ssuch: QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap());...
-
Hello all, I've been wrestling with this issue for a while, and I'm at my wit's end, so here we go. I'm trying to follow Florian's instructions to instantiate a class, as per this thread from many years ago: https://sourceforge.net/p/pythonqt/discussion/631393/thread/6a851191/. I would then like to call methods of this class. To do this, I am trying to return an instance of the class as ssuch: QVariant instance = PythonQt::self()->getMainModule().call("HelloWorld", QVariantList(), QVariantMap());...
-
Hi all, So, I'd like to start by saying that PythonQt seems incredibly useful, but it does sadden me with it's lack of documentation. I'm trying to ascertain the difference between a decorator and a custom class wrapper, as per https://doc.qt.io/archives/qq/qq23-pythonqt.html, the PyCPPWrapperExample vs. PyDecoratorsExample. Is there an advantage to one over the other? They seem to be doing incredibly similar things, excapt that one requires an addDecorators call. Thanks a bunch.
-
Yes, I never implemented this. I think it requires special support by PythonQt. On Fri, Nov 8, 2019 at 3:24 PM Max galicarnax@users.sourceforge.net wrote: I had no trouble creating QTreeView and connecting it to QAbstractTableModel on the Python side of PythonQt. Now I need to create a custom model by subclassing QAbstractItemModel, and I just can't make it working. Help is appreciated. Basically, the problem is with the createIndex() method, which accepts row/column and a pointer to a custom tree-item...
-
Max modified a comment on discussion Help
I had no trouble creating QTreeView and connecting it to QAbstractTableModel on the Python side of PythonQt. Now I need to create a custom model by subclassing QAbstractItemModel, and I just can't make it working. Help is appreciated. Basically, the problem is with the createIndex() method, which accepts row/column and a pointer to a custom tree-item object. Since in Python there are no pointer, I tried passing just the object itself (as usual), but it failed with errors like this one: ValueError:...
-
I had no trouble creating QTreeView and connecting it to QAbstractTableModel on the Python side of PythonQt. Now I need to create a custom model by subclassing QAbstractItemModel, and I just can't make it working. Help is appreciated. Basically, the problem is with the createIndex() method, which accepts row/column and a pointer to a custom tree-item object. Since in Python there are no pointer, I tried passing just the object itself (as usual), but it failed with errors like this one: ValueError:...
-
C extensions are typically not deployed in debug mode (there are no wheels for them) and building them yourself in debug mode can be difficult or even mostly impossible (scipy for example is really hard to build yourself on Windows). So you can choose between tryping to get a debug build running (which almost nobody of the Python community uses), or to live with a release build. The VS debugger works on release mode as well, so it may not be such a big limitation. Anyways, it is not a PythonQt issue,...
-
David Brooks posted a comment on discussion Help
Specific DLLs may or may not work with each other, depending on respective compiler options at build time (Google or see here https://stackoverflow.com/questions/11658915/mixing-debug-and-release-library-binary-bad-practice for background). DLLs for the standard modules are built as part of Python (they are the files in Python's lib/lib-dynload directory); numpy is not part of standard Python, so is built by separately. Did you build your own Python?? It's only those modules that provide DLLs (pyd...
-
Nick Bowsher posted a comment on discussion Help
wow. That actually sounds quite tedious considering all the site packages one can use in a project. Does anyone know how to get some precompiled debug module libraries for windows ?(from OSGeo maybe?). And that still does't solve the mystery as to why the standard modules such as os or sys run in debug and release mode. (I don't see any debug libraries for those in my distro yet they work)
-
wow. That actually sounds quite tedious considering all the site packages one can use in a project. Does anyone know how to get some precompiled debug module libraries for windows ?(from OSGeo maybe?). And that still does't solve the mystery as to why the standard modules such as os or sys run in debug and release mode. (I don't see any debug libraries for those in my distro yet they work)
-
If you are in debug mode then you need a debug version of numpy's shared libraries, which means building a debug version of numpy yourself. Windows can't mix Debug and Release mode DLLs. On 13/09/19 9:34 PM, Nick Bowsher wrote: Alright so I solved my problem. The whole time I was on Debug mode and the external package imports would not work for whatever reason. Even though I correctly linked all debug libs etc. Luckily I just switched over to release mode and everything is working fine now. It wouldn't...
-
Alright so I solved my problem. The whole time I was on Debug mode and the external package imports would not work for whatever reason. Even though I correctly linked all debug libs etc. Luckily I just switched over to release mode and everything is working fine now. It wouldn't be bad to know why it doesn't work in Debug mode though.
-
Marius Alexander modified a comment on discussion Help
Hello, I have a very similar error when importing numpy. It occures when numpy wants to import numpy.core._muliarray_umath, but exits with "undefined symbol: PyExc_ImportError": import numpy as np Traceback (most recent call last): File "pathToPython37/lib/python3.7/site-packages/numpy/core/init.py", line 17, in <module> from . import multiarray File "pathToPython37/lib/python3.7/site-packages/numpy/core/multiarray.py", line 14, in <module> from . import overrides File "pathToPython37/lib/python3.7/site-packages/numpy/core/overrides.py",...
-
Hello, I have a very similar error when importing numpy. It occures when numpy wants to import numpy.core._muliarray_umath, but exits with "undefined symbol: PyExc_ImportError": import numpy as np Traceback (most recent call last): File "pathToPython37/lib/python3.7/site-packages/numpy/core/init.py", line 17, in <module> from . import multiarray File "pathToPython37/lib/python3.7/site-packages/numpy/core/multiarray.py", line 14, in <module> from . import overrides File "pathToPython37/lib/python3.7/site-packages/numpy/core/overrides.py",...
-
Hello, I have a very similar error when importing numpy. It occures when numpy wants to import numpy.core._muliarray_umath, but exits with "undefined symbol: PyExc_ImportError": import numpy as np Traceback (most recent call last): File "*pathToPython37*/lib/python3.7/site-packages/numpy/core/__init__.py", line 17, in <module> from . import multiarray File "*pathToPython37*/lib/python3.7/site-packages/numpy/core/multiarray.py", line 14, in <module> from . import overrides File "*pathToPython37*/lib/python3.7/site-packages/numpy/core/overrides.py",...
-
Can you try to add these paths to the system PATH variable? Might be worth a try. (1) D:\python37\Library\mingw-w64\bin (2) D:\python37\Library\usr\bin (3) D:\python37\Library\bin (4) D:\python37\Library\Scripts (5) D:\python37\bin You can do that in the python console, too: import os os.environ['PATH'] += ";(1);(2);(3);(4);(5)" import numpy
-
Hello, I have a very similar error when importing numpy. It occures when numpy wants to import numpy.core._muliarray_umath, but exits with "undefined symbol: PyExc_ImportError": import numpy as np Traceback (most recent call last): File "pathToPython37/lib/python3.7/site-packages/numpy/core/init.py", line 17, in <module> from . import multiarray File "pathToPython37/lib/python3.7/site-packages/numpy/core/multiarray.py", line 14, in <module> from . import overrides File "pathToPython37/lib/python3.7/site-packages/numpy/core/overrides.py",...
-
Hello, I have a very similar error when importing numpy. It occures when numpy wants to import numpy.core._muliarray_umath, but exits with "undefined symbol: PyExc_ImportError": import numpy as np Traceback (most recent call last): File "pathToPython37/lib/python3.7/site-packages/numpy/core/init.py", line 17, in <module> from . import multiarray File "pathToPython37/lib/python3.7/site-packages/numpy/core/multiarray.py", line 14, in <module> from . import overrides File "pathToPython37/lib/python3.7/site-packages/numpy/core/overrides.py",...
-
Hello, I have a very similar error when importing numpy. It occures when numpy wants to import numpy.core._muliarray_umath, but exits with "undefined symbol: PyExc_ImportError": import numpy as np Traceback (most recent call last): File "<path to="" python37="">/lib/python3.7/site-packages/numpy/core/init.py", line 17, in <module> from . import multiarray File "<path to="" python37="">/lib/python3.7/site-packages/numpy/core/multiarray.py", line 14, in <module> from . import overrides File "<path...
-
yes, for autocompletion. I have not yet adapted toconsole, becausewe have our own console in our product. It just needs additional GIL scope locks to work with threading.
-
Thanks for your help. The problem was that I am using PythonQtScriptingConsole, and after releasing the GIL, the app seg-faulted whenever I just typed into the console (without even pressing Enter). But if I do not interact with the console but just evaluate a script from my c++ app, then python threads run normally without blocking my c++ app. (Still, it's a bit surprising that seg-fault happens when I type a single letter in the console -- is python interpreter invoked without even pressing En...
-
Thanks for your help. The problem was that I am using PythonQtScriptingConsole, and after releasing the GIL, the app seg-faulted whenever I just typed into the console (without even pressing Enter). But if I do not interact with the console but just evaluate a script from my c++ app, then python threads run normally without blocking my c++ app. (Still, it's a bit supprising that seg-fault happens when I type a single letter in the console -- is python interpreter invoked without even pressing En...
-
Thanks for your help. The problem was that I am using PythonQtScriptingConsole, and after releasing the GIL, the app seg-faulted whenever I just typed into the console (without even pressing Enter). But if I do not interact with the cnsole but just evaluate a script from my c++ app, then python threads run normally without blocking my c++ app. (Still, it's a bit supprising that seg-fault happens when I type a single letter in the console -- is python interpreter invoked without even pressing Ent...
-
First of all thumbs up for this very useful tool! I have created a custom console just as done in the PyScriptingConsole provided with the source code. Everything works fine except there seems to be issues when attempting to load numpy on Python 3.7.4 Yes, I have removed PythonQt::IgnoreSiteModule and yes, I do have the very latest version of numpy installed via pip. It also runs perfectly if I start python from cmd.exe in Windows. if I input the following in my app though I get: py>import sys py>sys.path.clear()...
-
First of all thumbs up for this very useful tool! I have created a custom console just as done in the PyScriptingConsole provided with the source code. Everything works fine except there seems to be issues when attempting to load numpy on Python 3.7.4 Yes, I have removed PythonQt::IgnoreSiteModule and yes, I do have the very latest version of numpy installed via pip. It also runs perfectly if I start python from cmd.exe in Windows. if I input the following in my app though I get: py>import sys py>sys.path.clear()...
-
Threading in PythonQt in fully functional and working. There is one thing that you have to keep in mind: By default, the main thread of your application will hold the GIL, so other threads can only get a time slice when the main thread is running in a Python loop. So what you have to do is to release the GIL after you started up PythonQt and retake it whenever you want to talk to Python from C++ from whatever thread. You release the GIL after the initial PythonQt initialization by: PythonQt::setEnableThreadSupport(true);...
-
Threading in PythonQt in fully functional and working. There is one thing that you have to keep in mind: By default, the main thread of your application will hold the GIL, so other threads can only get a time slice when the main thread is running in a Python loop. So what you have to do is to release the GIL after you started up PythonQt and retake it whenever you want to talk to Python from whatever thread. You release the GIL after the initial PythonQt initialization by: PythonQt::setEnableThreadSupport(true);...
-
So, in 2019 closing to the end, what is the status of threading module support in PythonQt? I see the PythonQt::setEnableThreadSupport(true) method in the docs, and I call it when my app starts. Nevertheless, when I start threads in embedded interpreter, they are not working as expected. NOTE: I am not asking for help - just a short answer if threading is supported in last version of PythonQt (as suggested by the existence of the above-mentioned method) or not. P.S. Below is the code I use in python....
-
So, in 2019 closing to the end, what is the status of threading module support in PythonQt? I see the PythonQt::setEnableThreadSupport(true) method in the docs, and I call it when my app starts. Nevertheless, when I start threads in embedded interpreter, they are not working as expected. NOTE: I am not asking for help - just a short answer if threading is supported in last version of PythonQt (as suggested by the existence of the above-mentioned method) or not. P.S. Below is the code I use in python....
-
So, in 2019 closing to the end, what is the status of threading module support in PythonQt? I see the PythonQt::setEnableThreadSupport(true) method in the docs, and I call it when my app starts. Nevertheless, when I start threads in embedded interpreter, they are not working as expected. NOTE: I am not asking for help - just a short answer if threading is supported in last version of PythonQt (as suggested by the existence of the above-mentioned method) or not. P.S. Below is the code I use in python....
-
Stanislaus Reitenbach modified a comment on discussion Help
Hello, is there a way to prevent the application from crashing if the PythonQt::init() function call fails due to an incorrect Python configuration? In my application the user can set the PYTHONHOME and PYTHONPATH path to an individual Python environment. If the chosen path does not lead to a Python environment or does not exist at all, the application crashes with the following error: Fatal Python error: initfsencoding: unable to load the file system codec Fatal Python error: unable to load the...
-
Hello, is there a way to prevent the application from crashing if the PythonQt::init() function call fails due to an incorrect Python configuration? In my application the user can set the PYTHONHOME and PYTHOnPATH path to an individual Python environment. If the chosen path does not lead to a Python environment or does not exist at all, the application crashes with the following error: Fatal Python error: initfsencoding: unable to load the file system codec Fatal Python error: unable to load the...
-
Thanks. So I guess I should follow the PyCPPWrapperExample example provided in PythonQt source-codes. If I understand correctly from CustomObjects.h, this example is exactly about using decorators rather than factory.
-
From a performance and memory consumption point of view, using decorators is the best solution. The decorator QObject only exists once and the decorator slots are cached, so that the lookup is fast. So registering a C++ object and adding decorators is the best. Deriving from QObject will add QObject overhead to your C++ class (which is not much, but if you have thousands of small C++ objects, it's better to avoid it). Using the CPP wrapper factory has extra overhead, since it creates a wrapper QObject...
1 >
