Strap in for a dev report cause stuff just got real
So I decided like any good dev to start the year with some commits and a new pypi release
This meant adding bob building to NekoMimi
Tiny issue... BOB DEPENDS ON NEKOMIMI
so you can't uninstall it then build it and reinstall it..
I said ok no problem let's just not uninstall it
Other issue comes up, it will always try to load the info from the site pkg location and not the local package
Then I came up with a genius and CURSED idea to IMPORT PIP AND UNINSTALL THE MODULE WHILE RUNNING THE SCRIPT!
new issue occurs!
YOU CAN'T IMPORT BOTH PIP AND SETUPTOOLS!
it was back to the drawing board..
Since I didn't want to include utils outside the main bob binary (script lol) I decided to include the necessary utilities from nekomimi directly into bob although I kinda didn't like that but ultimately it was the only way I could do what I want with the rules I set, also no btw frick getting the spec and building a module from the spec I ain't doing that
So now I implemented the first half which is the main utils submodule and it works nicely
The issue is with colourimi and the class/object inheritance mess, everything is fricked
And I don't want to unsandbox the colourimi module since it exposes many unnecessary methods
But ah well
Lesson learned ig
Stick to c++
No actually I'm not kidding
Since the way the preprocessor handles includes is by pasting the included file, so I'll just paste colourimi as is and cope with the unnecessary methods I added
[#]foss #programming_nightmare
=> More informations about this toot | More toots from nekomimi@sakurajima.moe
text/gemini
This content has been proxied by September (ba2dc).