I think that a custom solution that sits on top of pip might make sense. Not in the immediate future, but long-term. In a lot of cases, iOS needs to be special-cased, and it's quite common that a few files have to be patched to get some packages working in Pythonista. I'm thinking of something like a curated directory that's based on whitelisting pypi packages and in some cases hosting patches.
To be clear though, those are just some ideas, not something I'm actively working on at the moment.
@JonB , yeah I know themes are handled in the editor module. At least for now. Themes are very complex, I know you know. So who knows we're they will end up once @omz thinks about it more. There are so many side effects with themes. Or let's say decisions to be made about implementation/API. maybe it will just stay in the editor module.even On my best day, I am glad it's not me deciding... It's very tricky
@JonB , after a long afternoon of trying understand the side effects I was creating, I have decided to go a different way. It gets worse when trying to add functionality to the class, which is the main intent. I am not giving up. I just dont think its a viable solution. I know you did it in a limited context.
I have thought of another way with just some wrapper functions. I am pretty sure i will be able to achieve almost all I wanted to do with a fraction of the code and side effects. Let's see 😱😳👍
I wil just declare I am an idiot. My lack of knowledge takes me on stupid journeys.if I had looked at dict class in more detail i would not been trying to write this class. Have dictviews also. But it's all been a learning process. After doing this, I feel a lot better equipped to try and understand dicts 100%