This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients aeros, eryksun, miss-islington, paul.moore, steve.dower, tim.golden, vstinner, xtreak, zach.ware
Date 2020-04-13.12:02:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586779330.85.0.439269631347.issue40214@roundup.psfhosted.org>
In-reply-to
Content
> But I'm not sure why that is getting loaded earlier than the 
> current directory. Is that the behaviour we went for here?

I don't understand what's going on here if %PATH% is interfering. The current directory (%__CD__%) should be checked before %PATH% with the standard DLL search order for desktop applcations. That's what I've observed in practice and how it's documented [1]:

    SafeDllSearchMode enabled:

    1. %__APPDIR__%
    2. %SystemRoot%\System32
    3. %SystemRoot%\System
    4. %SystemRoot%
    5. %__CD__%
    6. %PATH%

    SafeDllSearchMode disabled:

    1. %__APPDIR__%
    2. %__CD__%
    3. %SystemRoot%\System32
    4. %SystemRoot%\System
    5. %SystemRoot%
    6. %PATH%

[1]: https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#search-order-for-desktop-applications
History
Date User Action Args
2020-04-13 12:02:10eryksunsetrecipients: + eryksun, paul.moore, vstinner, tim.golden, zach.ware, steve.dower, miss-islington, xtreak, aeros
2020-04-13 12:02:10eryksunsetmessageid: <1586779330.85.0.439269631347.issue40214@roundup.psfhosted.org>
2020-04-13 12:02:10eryksunlinkissue40214 messages
2020-04-13 12:02:10eryksuncreate