Re: [Development] [EXTERNAL EMAIL] Re: Repository request: playground/qtscrypt
On 9/1/22 17:37, Mark De Wit wrote: This sounds like QPyBind11 to me? Hey Mark, Not really, pybind11 is a binding generation system like the one used for the Qt for Python project, Shiboken. The idea of PyBind11 (and Shiboken) is to expose C++ API to Python users, meaning that you end up writing a Python script using modules that originate in C++. The idea of this project, as stated in the previous messages, is to have Python code (as a string) within your C++ code. No binding is generated, no wrapper, is just a usage of the Python interpreter C-API within C++. Mark [snip] Cheers! -- Dr. Cristián Maureira-Fredes Senior R&D Manager The Qt Company GmbH Erich-Thilo-Str. 10 D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Repository request: playground/qtscrypt
> On 31 Aug 2022, at 16:47, Cristián Maureira-Fredes > wrote: > > Hey there, > > I would like to request a new repository on codereview.qt-project.org > > Name and description: qtscrypt - Script C++ with Python > Responsible person: Cristián Maureira-Fredes (cristian.maureira-fre...@qt.io) > Desired repository name: playground/qtscrypt > URL of existing code: https://git.qt.io/crmaurei/qtscrypt > > Thanks The discussion gives me the impression that any repository or module name is going to be confusing for people not reading the fine-print, and of what has been proposed, QtPythonScripting makes the most sense to me (in that it explicitly is not QtPythonBinding). This will be a playground project, so the naming doesn’t need to be perfect yet. If and when it becomes a place of collaboration, perhaps the hive-mind of contributors produces the perfect name. +1 to go ahead with QtPythonScripting as the name and repository. Volker ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Repository request: playground/qtscrypt
+1 to go ahead with QtPythonScripting as the name and repository. +1, QtPythonScripting seems like the least confusing option to me, too. You can still have a "marketing name" different from the repository and/or module name then. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Repository request: playground/qtscrypt
On 9/2/22 16:15, Volker Hilsheimer wrote: On 31 Aug 2022, at 16:47, Cristián Maureira-Fredes wrote: [snip] +1 to go ahead with QtPythonScripting as the name and repository. Work for me as well, Thanks Volker Cheers -- Dr. Cristián Maureira-Fredes Senior R&D Manager The Qt Company GmbH Erich-Thilo-Str. 10 D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Repository request: playground/qtscrypt
On Fri, Sep 02, 2022 at 02:15:15PM +, Volker Hilsheimer wrote: +1 to go ahead with QtPythonScripting as the name and repository. how about QtPyScript? that's not so long, and makes the parallel to QtScript very obvious. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
