On Monday, August 12, 2019 at 9:59:05 AM UTC-5, Edward K. Ream wrote: > The new scheme is the *only* way that has any realistic chance of working.
*Implications* 1. We can now see clearly we must import *all* of pyzo's code into Leo. Exactly where doesn't matter. We can't adapt pyzo to Leo in any other way. This is a significant commitment for future devs. Imo, it's probably worth doing, but we should confront the costs, particularly... 2. Comments of the form #EKR:change-(why)mark all significant changes. In future, if we want to take advantage of updates to pyzo, we would have to retro-fit those EKR changes back into the updated copy of pyzo's sources. This would likely take only a few hours. The alternatives would be much worse. Experience shows that we shouldn't even think about monkey-patches. Edward -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c87a246b-62d3-406b-9b88-0ede10310856%40googlegroups.com.
