Skip to content

Windows: conda-standalone may fail with no OPENSSL_Applink with official Python installed #86

@marcoesters

Description

@marcoesters

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

Some users report failures with Miniconda 24.5.0, which uses conda-standalone 24.5.0 as the bootstrapper. One example can be found here: ContinuumIO/anaconda-issues#13408

Further debugging showed that the release binaries for conda-standalone 24.5.0 produce the same error:

OPENSSL_Uplink(00007FFB01AE2FE8,08): no OPENSSL_Applink

There appears to be a correlation with users having an official Python installed. I cannot reproduce the problem though.

Miniconda 24.4.0, which uses conda-standalone 24.3.0, works fine though.

Conda Info

N/A

Conda Config

N/A

Conda list

N/A

Additional Context

A lot of things have changed between conda-standalone 24.3.0 and 24.5.0, most notably the Python and pyinstaller versions got updated.

However, the packages on defaults were both built with pyinstaller 5.13.2.

Metadata

Metadata

Assignees

No one assigned

    Labels

    locked[bot] locked due to inactivitytype::bugdescribes erroneous operation, use severity::* to classify the type

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions