Open GitPeterJ opened 10 months ago
I had the same thing, I was using python 3.10. My gut feeling is the process involves snipping the "3.??" string hence it was trying to refer the "python3.1/...." paths.
I switched to python 3.9 and this error disappeared. But you are right this is indeed a bug :)
The problem is that the version is being snipped, while searching for a solution I saw that the first approach was to do it like str[:3]
, but this was already fixed (don't remember which commit). So I am confused about why this is still a problem, 2 years after 3.10 was released! Also downgrading to 3.9 should not be a final solution as this version will be phased out.
An unsynchronized conda-meta directory can cause the same problem. When updating certain packages, conda can update the packages without updating corresonding json files in conda-meta (i.e. updating pytorch 2.4.0-cuda12.1 from 2.1.2-cuda12.1). Such behavior does not affect the functions of conda environment, but leads to confusion while launching conda pack. I think a force mode that ignores conda-meta and simply pack any files within the env directory can be a solution.
Checklist
What happened?
While trying to create a packaged environment for Triton server I get an error when I run the conda-pack command. In the error I see it's trying to get packages from the python3.1 folder, I saw a previous bug report where this was fixed but apparently, it's still a problem.
*ERROR
Collecting packages... CondaPackError: Files managed by conda were found to have been deleted/overwritten in the following packages:
This is usually due to
pip
uninstalling or clobbering conda managed files, resulting in an inconsistent environment. Please check your environment for conda/pip conflicts usingconda list
, and fix the environment by ensuring only one version of each package is installed (conda preferred).Conda Info
Conda Config
Conda list
Additional Context
No response