Ruff import broken on latest release

[akhmerov]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

To reproduce, create an empty environment and execute

mamba install -y ruff
python -c "import ruff" # Error
pip install ruff --force-reinstall
python -c "import ruff" # Success

Installed packages

Name              Version     Build               Channel    
─────────────────────────────────────────────────────────────────
  _libgcc_mutex     0.1         conda_forge         conda-forge
  _openmp_mutex     4.5         2_gnu               conda-forge
  bzip2             1.0.8       hd590300_5          conda-forge
  ca-certificates   2023.11.17  hbcca054_0          conda-forge
  ld_impl_linux-64  2.40        h41732ed_0          conda-forge
  libexpat          2.5.0       hcb278e6_1          conda-forge
  libffi            3.4.2       h7f98852_5          conda-forge
  libgcc-ng         13.2.0      h807b86a_3          conda-forge
  libgomp           13.2.0      h807b86a_3          conda-forge
  libnsl            2.0.1       hd590300_0          conda-forge
  libsqlite         3.44.2      h2797004_0          conda-forge
  libstdcxx-ng      13.2.0      h7e041cc_3          conda-forge
  libuuid           2.38.1      h0b41bf4_0          conda-forge
  libzlib           1.2.13      hd590300_5          conda-forge
  ncurses           6.4         h59595ed_2          conda-forge
  openssl           3.2.0       hd590300_1          conda-forge
  pip               23.3.2      pyhd8ed1ab_0        conda-forge
  python            3.12.0      hab00c5b_0_cpython  conda-forge
  python_abi        3.12        4_cp312             conda-forge
  readline          8.2         h8228510_1          conda-forge
  ruff              0.1.9       py312h9118e91_0     conda-forge
  setuptools        68.2.2      pyhd8ed1ab_0        conda-forge
  tk                8.6.13      noxft_h4845f30_101  conda-forge
  tzdata            2023d       h0c530f3_0          conda-forge
  wheel             0.42.0      pyhd8ed1ab_0        conda-forge
  xz                5.2.6       h166bdaf_0          conda-forge

Environment info

libmamba version : 1.5.3
     micromamba version : 1.5.3
           curl version : libcurl/8.4.0 OpenSSL/3.1.4 zlib/1.2.13 zstd/1.5.5 libssh2/1.11.0 nghttp2/1.58.0
     libarchive version : libarchive 3.7.2 zlib/1.2.13 bz2lib/1.0.8 libzstd/1.5.5
       envs directories : /home/anton/micromamba/envs
          package cache : /home/anton/micromamba/pkgs
                          /home/anton/.mamba/pkgs
            environment : test (active)
           env location : /home/anton/micromamba/envs/test
      user config files : /home/anton/.mambarc
 populated config files : /home/anton/.condarc
       virtual packages : __unix=0=0
                          __linux=6.5.0=0
                          __glibc=2.38=0
                          __archspec=1=x86_64-v3
               channels : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
       base environment : /home/anton/micromamba
               platform : linux-64

[bollwyvl]

The latest release (0.1.11) and presumably 0.1.10 also has this issue.

I've updated #154, which tests for this condition, for 0.1.11: this would probably help keep the robots from continuing to ship packages without the python entry point, used by a number of downstreams.

[sogoodmo]

Hey it looks like this issue is solved in 0.1.13 -- I think it's okay to close now? astral-sh/ruff#9401

[akhmerov]

I confirm, the problem is solved for me. Closing.

[bollwyvl]

yes, but would still worthwhile adding the test: {imports: [ruff]} so this doesn't happen again