Yeah that is to be expected as the python API changes quite significantly. But plugin authors tend to update the plugins, and I know some of them are already V7 compatible. You will need to update the plugins though. But I imagine that it will not take a year (when V8 is planed for release) for the plugin authors to update them.
I am afraid though that when V8 comes out, we’ll go thorugh the same process again.
The could, but then the plugin authors would most likely (me included) be the main reason for the delay of the KiCad release.
I personally write and support the plugins as a volunteer effort. I started writing the plugins because I needed the feature in KiCad, but supporting the plugin is an effort to “make the world a better place”. But this effort can quickly be superseded by other aspects of my life, so I maintain the plugins only when I have the time. Without the regard for KiCad release schedule.
On Windows things are simpler as KiCad supplies its own python interpreter. So when I used to develop the plugins there it was quite easy to test the business logic of the plugin within PyCharm IDE (or similar) You would just point the IDE to use the KiCad’s interpreter.
On Linux KiCad uses system interpreter and with V6 it used to put the python bindings so that the system interpreter could see them.
With V7 I had to:
add path /usr/lib/kicad/lib/python3/dist-packages to the interpreter (File/Settings/Project/Python Interpreter/Show all/Show interpreter paths/Add)
add environemnt variable LD_LIBRARY_PATH containing paths to /usr/lib/kicad/lib/python3/dist-packages/:/usr/lib/kicad/lib/x86_64-linux-gnu/ to the debug(run) configuration (Run/Edit configuration/Edit environment variables)
The whole problem is that without third-party plugins it is not possible and they are not made by the developers of kicad, so it makes sense to write if they deliberately changed the python api for plugins… Two options remain is a return to version 6 or a long wait for version 7 fixes if they are at all for plugins
There is always a third way. Don’t be so eager when switching Kicad versions. If you switch when x.0.1 version is released, by that time most of the serious/responsible plugin maintainers will release x.0 compatible version. And for those that don’t, this should be a good indicator that it is risky to base your work on their solutions.