Cannot git commit without python3.11

[jjimenezshaw]

Problem description

I cannot do a commit.

The file .pre-commit-config.yaml
requires python3.11

default_language_version:
    python: python3.11

However, after installing the conda environment as explained in https://github.com/jjimenezshaw/pyproj/blob/main/CONTRIBUTING.md

The error message when trying to do a commit is:

An unexpected error has occurred: CalledProcessError: command: ('/home/jshaw/anaconda3/envs/pyproj-devel/bin/python', '-mvirtualenv', '/home/jshaw/.cache/pre-commit/repoc6h5_c3j/py_env-python3.11', '-p', 'python3.11')
return code: 1
stdout:
    RuntimeError: failed to find interpreter for Builtin discover of python_spec='python3.11'
stderr: (none)
Check the log at /home/jshaw/.cache/pre-commit/pre-commit.log

The installed python in the environment is

$ python3 --version
Python 3.13.7

Expected Output

I can do commits following the instructions.

Environment Information

• Ubuntu 24.04

Installation method

• conda

Conda environment information (if you installed with conda):

Details about conda and system ( conda info ):

$ conda info

     active environment : pyproj-devel
    active env location : /home/jshaw/anaconda3/envs/pyproj-devel
            shell level : 1
       user config file : /home/jshaw/.condarc
 populated config files : /home/jshaw/anaconda3/.condarc
                          /home/jshaw/.condarc
          conda version : 25.5.1
    conda-build version : 25.5.0
         python version : 3.13.5.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=icelake
                          __conda=25.5.1=0
                          __glibc=2.39=0
                          __linux=6.8.0=0
                          __unix=0=0
       base environment : /home/jshaw/anaconda3  (writable)
      conda av data dir : /home/jshaw/anaconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/jshaw/anaconda3/pkgs
                          /home/jshaw/.conda/pkgs
       envs directories : /home/jshaw/anaconda3/envs
                          /home/jshaw/.conda/envs
               platform : linux-64
             user-agent : conda/25.5.1 requests/2.32.3 CPython/3.13.5 Linux/6.8.0-79-generic ubuntu/24.04.3 glibc/2.39 solver/libmamba conda-libmamba-solver/25.4.0 libmambapy/2.0.5 aau/0.7.1 c/. s/. e/.
                UID:GID : 1001:1001
             netrc file : None
           offline mode : False

[djhoese]

I wonder if the various hooks could have their specific flags specified to say what version of python to perform their checks against. As is, this is requiring that a Python 3.11 interpreter be available specifically.

[snowman2]

I have it set for the minimum python version pyproj supports. Pinning the Python version ensures consistency. However, that consistency comes at the cost mentioned in this issue.

[djhoese]

I guess what I was trying to say is that some tools can do checks targeting a specific version of python without needing to run as that version.

[jjimenezshaw]

Is there a way in conda to install python3.11, so it is available for the pre-commit, but still use python3.13 for the rest?

[snowman2]

I usually use deadsnakes

pyproj/.github/workflows/tests.yaml

Line 57 in 2d991e1

add-apt-repository -y ppa:deadsnakes/ppa

[jjimenezshaw]

I usually use deadsnakes

Can it be only in the conda environment? How?

[snowman2]

I usually use deadsnakes

Can it be only in the conda environment? How?

If you create a new conda environment with Python 3.11 and asd the bin directory to PATH, that should work as well.