cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake | IRC logs: and | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
<arigato> mattip: what is the mechanism to add dll directories at startup? I don't see how it can be done other than writing some custom C code---in other words, they need to write a custom version of pypy3.exe anyway, no?
<arigato> randomly looking at python-dev, I see that it's still the same infinite discussions going everywhere but a more agressive tone than I remember. E.g. Guido is told he doesn't understand what it's about, he politely answers that he'll leave the discussion then, and nobody else finds that strange
<arigato> and of course cfbolz injecting a "pypy has always done that and it works" and is entirely ignored
<arigato> (but that last part is not new)
ltfish has quit [Ping timeout: 248 seconds]
ltfish has joined #pypy
jcea has quit [Ping timeout: 260 seconds]
pbsds has quit [Quit: The Lounge -]
pbsds has joined #pypy
Atque has quit [Ping timeout: 255 seconds]
Atque has joined #pypy
<LarstiQ> snow! snow!
ltfish has quit [Ping timeout: 265 seconds]
ltfish has joined #pypy
<cfbolz> arigato: oh, which thread was that?
<cfbolz> the 'None' one?
epony has quit [Quit: QUIT]
derpydoo has quit [Quit: derpydoo]
derpydoo has joined #pypy
epony has joined #pypy
derpydoo has quit [Quit: derpydoo]
<mattip> arigato: conda patches pypy with this
<mattip> that adds a function CondaEcosystemModifyDllSearchPath_Init() to call add_dll_directory()
<mattip> so the custom C code is already written. The question is when to call it
<mattip> currently this is called as part of app_main, which solves find dlls for all the cffi c-extensions
jcea has joined #pypy