Ken Odegard

It appears that we depend on several **not** `noarch: python` packages which will need to be rebuilt for Python 3.11. See e.g., `conda search --info anaconda-client`:

@dholth Good idea to add this to the skip blame after merging. I've added a news snippet. Unsure where to add additional rebasing instructions. I just tried rebasing several PRs...

On the development branch I tested both rebase and merge resulted in 5 conflicts needing manual fixes. Either way, these conflicts were easy to work through, so I don't see...

I am unable to replicate this issue - what command did you run?

@marscher looks like the recipe needs to be something like: ```yaml {% set pyproject = load_file_data("../../pyproject.toml", from_recipe_dir=True) %} {% set proj = pyproject.get('project') %} # ... entry_points: {% for module,...

@MazelTovy `conda` v3.16.0 was released 6 year ago, can you try a newer `conda`?

Since you appear to have successfully installed `conda` v3.16.0 I would suggest trying a normal update: ```bash conda update conda ```

Probably not for another year or so. Looking at the changes here now I'm not sure there's value in doing the string reformatting as I did. Too much noise.

Here is the env vars that are displayed: https://github.com/conda/conda/blob/c75b4b561676af9a3c7946664351564725c5dd2f/conda/cli/main_info.py#L191-L202

@pavelzw hm no idea why I didn't merge this earlier, thanks for poking me