Cannot import deeplay with a version of python greater than 3.12

[H3pha1stos]

Hi,

It seems that the 'deeplay' library cannot be imported when using python (3.13 or 3.14).

`
Error trace:Python 3.13.9 (main, Oct 14 2025, 13:52:31) [Clang 17.0.0 (clang-1700.3.19.1)] on darwin

import deeplay as dl

Traceback (most recent call last):

File "", line 1, in

import deeplay as dl

File "/Users/X/Downloads/test/.venv/lib/python3.13/site-packages/deeplay/init.py", line 14, in

from .blocks import *

File "/Users/X/Downloads/test/.venv/lib/python3.13/site-packages/deeplay/blocks/init.py", line 9, in

from .conv import Conv2dBlock

File "/Users/X/Downloads/test/.venv/lib/python3.13/site-packages/deeplay/blocks/conv/init.py", line 3, in

from .conv2d import Conv2dBlock

File "/Users/X/Downloads/test/.venv/lib/python3.13/site-packages/deeplay/blocks/conv/conv2d.py", line 7, in

from deeplay.blocks.base import BaseBlock

File "/Users/X/Downloads/test/.venv/lib/python3.13/site-packages/deeplay/blocks/base.py", line 2, in

from re import A, T

ImportError: cannot import name 'T' from 're' (/opt/homebrew/Cellar/python@3.13/3.13.9_1/Frameworks/Python.framework/Versions/3.13/lib/python3.13/re/init.py)
``
Environment:

• macOS (Apple Silicon)

• Python: 3.13.9 (also reproduced on 3.14)

• deeplay: Installed via pip in a fresh virtual environment

Steps to reproduce:

1. Create a virtual environment using Python 3.13 or 3.14.

2. ‎pip install deeplay

3. ‎python -c "import deeplay"

Expected behavior:
Module imports successfully.

Actual behavior:
ImportError occurs due to ‎from re import A, T in ‎deeplay/blocks/base.py. The ‎re.T constant appears to be unavailable in Python ≥ 3.13.

Questions:

• Is Python 3.13+ currently supported?

• If not, is there a roadmap or planned fix to remove or replace the ‎re.T import?

Thank you for your answer

[giovannivolpe]

At the moment we explicitly support up to Python 3.12 (and unit test accordingly).
However, we're planning to extend support at least to Python 3.13 and possibly 3.14 in the following months now that they are supported by the latest version of PyTorch. We're running some tests to check that this doesn't break other parts of the code.

Actually, re.T is not used in the current version, so we have now removed the corresponding imports in the develop branch.
Could you try to test that?

[H3pha1stos]

Removing the import resolved the issue. Thanks for the help 👍🏻