Homemade plugin not found by daq_viewer

[aline-vernier]

Hello !
My home-grown plugin is now working with pip (full install in a fresh environment), but I can't seem to be able to make it work using install -e . in my dev. environment from the folder where I'm developing it. The python .egg.link appears in the site-packages folder, but the plugin is not seen by daq_viewer. I could of course make a fresh install and redevelop from there, but I'd like to understand why it's not working right now.
I hope my question is clear enough...
Best wishes !

Aline

[seb5g]

What is saying the log file?

[aline-vernier]

Sorry I forgot to mention the log file doesn't say anything about looking in the pymodaq_plugins_tango library... True enough, no information is information indeed ;)

[seb5g]

Without more info le will be difficult to help. Could you share your GitHub repo? Le ven. 17 janv. 2025, 14:24, aline-vernier ***@***.***> a écrit :

…

Sorry I forgot to mention the log file doesn't say anything about looking in the pymodaq_plugins_tango library... True enough, no information is information indeed ;) — Reply to this email directly, view it on GitHub <#510 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSNYI7UM3ZPTWQZA3CGMS32LEAAZAVCNFSM6AAAAABVKF2AEKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBWGY4TONY> . You are receiving this because you commented.Message ID: ***@***.***>

[aline-vernier]

Hullo :) My GH repo is https://github.com/PyMoDAQ-LOA/pymodaq_plugins_tango for the record, but I have given up on this for the moment as I have a fix (fresh environment, install from pip, and install -e . from the dev repo). I have more questions for which I don't have a fix, which I'll ask on the forum shortly.
I'd love to have a chat about best practices at some point if that's possible. When I have a clean and working plugin, I'll write a good documentation as proposed by @quantumm in another thread.
Thanks for being so responsive !

[aline-vernier]

I could not find the cause of this very particular issue, but a fresh install fixed the problem. Choose your battles wisely ;)