Hi! We have noticed when building Python containers including AtriumDB we see long build times to satisfy some of the older requirement, Pandas and MariaDB in particular. Those currently specified in AtriumDB don't have published wheels for newer versions of Python (3.12, 3.13 etc.) leading to this issue.
We have tried building the package with overridden newer requirements and all is working well on our end. However, we're not sure what your internal policies are for pinning these requirements to older/stable versions, or what internal testing you run.
Not a major issue but just something to flag. Happy to open a PR if you have any info on how you manage the requirements.
Thanks!
Hi! We have noticed when building Python containers including AtriumDB we see long build times to satisfy some of the older requirement, Pandas and MariaDB in particular. Those currently specified in AtriumDB don't have published wheels for newer versions of Python (3.12, 3.13 etc.) leading to this issue.
We have tried building the package with overridden newer requirements and all is working well on our end. However, we're not sure what your internal policies are for pinning these requirements to older/stable versions, or what internal testing you run.
Not a major issue but just something to flag. Happy to open a PR if you have any info on how you manage the requirements.
Thanks!