> > ... Leo's lack of an integrated shell drove me to pyzo. > Ditto. That and being able to inspect variable contents at runtime by double-clicking on them.
it would be rare to have both pyzo and Leo open at the same time. But that > would "just work" if you actually do that. > Yup, it just works! And is my standard operating procedure when I'm working on pure python stuff, which is more often than Python + Leo stuff. So, normal and not rare (for me). There is some friction with it tho: ...multiple editors/IDEs open ... is often messy and the "integrated" > component of IDE gets lost. > Which makes me somewhat sad, however, I too am not: ... implying that you do more work; it is your Leo, we just use it. ... > thank you for the recent work, very much appreciated. Absolutely! Switching to a different thread-in-the-thread: .... a pithy comment is way more effective than windy ones. > Yes. While being ware it's frightfully easy to intend pithy and be heard pissy, which is how I first read: ...not going to happen. Get used to it. > Pissy was likely not the intended tone here. A dance where we all step and misstep on both sides of the line. ;-) Anyway, back to the core: cutting down to python 3 and adding moveable docks are milestones to be celebrated. If thinking-via-code in pyzo integration experiments made that happen, then yay the experiments. (Sez me who didn't have skin in that game.) -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a3733729-d858-467b-98ce-d92c6345f683%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
