Forgot to say that I'd be happy to just edit the python code (in its installation dir) "in-place", but that carries the risk that conda may overwrite all my changes when it updates that package.
On Tue, Jun 4, 2024 at 2:59 PM Stefan Monov <logix...@gmail.com> wrote: > Hi all! Several questions. I'm on Windows and using radioconda. > > 1. How do I check if a module is written fully in python (rather than C++ > or both)? > 2. If I find out that it's written in python, how do I fork it (for my > personal use)? > > > I could do the following: > > 1. find the relevant github repo on google > 2. check if there are any *.cc/*.cpp files in it (to answer question 1) > 3. clone/download the repo > 4. look for all places in it that mention its name and change all of them > to my custom module name > 5. make my changes in the python code > 6. somehow tell GRC where to find my forked version > > > But this has some problems: > > - it's a bit of a hassle, and not very easy for less computer-savvy people > (like my friend for whom I'm researching this. He knows Python but is still > not a computer whiz) > - If there are *.cc files but only for QA/unittesting, I'm not sure if I > need to compile those. > > > I'm hoping to maybe simply copy&paste the python code (from the installed > conda package) into some custom dir of my choice, and point GRC to that > dir. But I'm not sure that'd work. And I'm not sure how to do make GRC find > my custom dir, or whether I need to put YML files in that dir. > > I've found tutorials on creating my custom module from scratch with > gr_modtool, but forking is a different usecase. > > Any pointers appreciated :) >
