Mark A. Hershberger

Do you have a url where we can see this?

From my JS console: ``` Uncaught TypeError: $slide.size is not a function jQuery 4 slideshow .../SemanticResultFormats/formats/gallery/resources/ext.srf.gallery.slideshow.js?91a37:88 jQuery 2 slideshow .../SemanticResultFormats/formats/gallery/resources/ext.srf.gallery.slideshow.js?91a37:57 .../extensions/SemanticResultFormats/formats/gallery/resources/ext.srf.gallery.slideshow.js?91a37:112 jQuery 2 .../extensions/SemanticResultFormats/formats/gallery/resources/ext.srf.gallery.slideshow.js?91a37:110 jQuery 9 .../SemanticResultFormats/formats/gallery/resources/ext.srf.gallery.slideshow.js?91a37:109 .../SemanticResultFormats/formats/gallery/resources/ext.srf.gallery.slideshow.js?91a37:116 jquery.responsiveslides.js:52:25 ```

When I use this patch on this project with this change: ``` diff @@ -1,4 +1,4 @@ -[tool.poetry] +[project] name = "poetry" version = "1.9.0.dev0" description = "Python dependency management...

Similar issue on debian: ``` $ rm -rf ~/.cache/pypoetry/ $ poetry config --list cache-dir = "~/.cache/pypoetry" experimental.system-git-client = false installer.max-workers = null installer.modern-installation = true installer.no-binary = null installer.parallel =...

In my testing the problem is in `virtualenv.cli_run` in [build_venv](https://github.com/python-poetry/poetry/blob/bd029ac0564b7822efbc903320e24ad021567a48/src/poetry/utils/env/env_manager.py#L678). Before that line: * Executable_str: ~/.asdf/installs/python/3.12.3/bin/python3.12 * sys: ~/.local/pipx/venvs/poetry/bin/python * args: ['--no-download', '--no-periodic-update', '--python', '.../.asdf/installs/python/3.12.3/bin/python3.12', '--prompt', 'devops-fabric-py3.12', '--no-wheel', '.../.cache/pypoetry/virtualenvs/devops-fabric-MXLzDq5t-py3.12'] This...

It looks like there is no `--python` parameter for current virtualenv. Instead, `--try-first-with` should be used.

Well, [there is](https://github.com/pypa/virtualenv/blob/0646a0544eedfe9c7666690ffe805a6d17cf6016/src/virtualenv/discovery/builtin.py#L34-L54) a `--python` but it looks like this needs `--try-first-with`.

1. An absolute path is provided. 2. `--python` [is documented, but so is](https://virtualenv.pypa.io/en/20.26.2/cli_interface.html#section-discovery) `--try-first-with`. Even though `--try-first-with` was [originally created for Windows where the wrong python interpreter was being found](https://github.com/pypa/virtualenv/pull/2046/commits/a3ad2acff045f970c88edcec055f89921aacb840),...

Since you mentioned the absolute path being passed to `--python`, it looks like this is closer to [this issue](https://github.com/pypa/virtualenv/issues/2659#issuecomment-1779555809) where the args are `--try-first-with=/usr/bin/python3.10 -p /usr/bin/python3.8` and the resulting environment...

I think I've found the source of my problem. It does not appear to have anything to do with the arguments. There was a leftover `~/.config/virtualenv/virtualenv.ini` containing ``` ini [virtualenv]...