As you have probably figured out by now, I don’t have experience with GRC. Your best answer will be to ask in the Matrix channel (or IRC if you are old-school).
I’m guessing your question is related to the change in how the Python bindings are done? I think that was 3.9 and not 3.10… In the next few months I’m looking to upgrade my GNU Radio version, so I’m glad you are on top of this :P --- Jim Melton Sr Principal Software Engineer Sierra Nevada Corporation 303.566.9582 (o) | 303.862.2459 (m) jim.mel...@sncorp.com<mailto:jim.mel...@sncorp.com> | sncorp.com<https://www.sncorp.com/> [cid:image002.jpg@01D8441B.D07F0260] From: Discuss-gnuradio <discuss-gnuradio-bounces+jim.melton=sncorp....@gnu.org> On Behalf Of Brandon Smith Sent: Wednesday, March 30, 2022 07:26 To: discuss-gnuradio@gnu.org Subject: [EXTERNAL] Removing Python Bindings from 3.9 OOT Hello, I am porting our GNURadio OOT from 3.8 to 3.9, and I have a block that we utilize only in C++ and do not expose in GRC/Python. What would be the correct method for removing it from the pybind process? I am hesitant to start removing it from the new bindings dir for fear of breaking the build. but from what I can gather: 1. remove block_python.cc 2. Remove block_python.cc from bindings/CMakeLists.txt 3. Remove mentions from python_bindings.cc Any other tips? Thank you! - Brandon Smith CONFIDENTIALITY NOTICE - SNC EMAIL: This email and any attachments are confidential, may contain proprietary, protected, or export controlled information, and are intended for the use of the intended recipients only. Any review, reliance, distribution, disclosure, or forwarding of this email and/or attachments outside of Sierra Nevada Corporation (SNC) without express written approval of the sender, except to the extent required to further properly approved SNC business purposes, is strictly prohibited. If you are not the intended recipient of this email, please notify the sender immediately, and delete all copies without reading, printing, or saving in any manner. --- Thank You.
