On Sat, Mar 28, 2020 at 6:57 AM Thomas Passin <[email protected]> wrote:
> I think I see the answer. When you change something in a Leo node, you do > not induce Python to re-compile any .pyc files in the various pycaches. > Updating a lib might invalidate cached calls *to* the lib if the lib's api changed. > If Leo had already loaded matplotlib earlier, then it would reuse that > compiled code when you did another matplotlib import from within Leo (e.g., > when trying out those examples). > Updating a lib had better invalidate the lib's caches. Otherwise python is broken. 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/CAMF8tS3Bcpcsk6U2eJEObA1hTk86B2bfpmJoxkZqW6CwFsQu%3Dg%40mail.gmail.com.
