Closed jfsmith-at-coveo closed 10 months ago
No specific reason, I just like to cap them at majors to make sure I don't accidentally introduce breaking changes, and then I lose track 😅 Let me bump it and test. If all goes fine I'll release today
Oh, I hear you. :sweat_smile: Many many thanks for a prompt reply!
Okay, so apparently the ward
testing framework I use caps it at >=12.2.0,<13.0.0
. I'll try to see what I can do about this.
Dealt with it, but I needed to cap python at >=3.7.8,<3.12
because of ward. I'll try to deal with ward
so that python>=3.12
is supported going forward. Here is the release: https://pypi.org/project/beaupy/3.7.2/
That's marvelous! Within the confines of my self-centered request, it's perfect, as I am still with python 3.11 at the moment. :) But knowing the python version limitation this forces on you, I'm very appreciative that you went ahead with this nonetheless. Thank you!
No worries. I will be glad if you'll find it useful 😊
Hi!
I would really love to use beaupy but my own project uses rich 13.7.0 whereas beaupy's pyproject.toml caps this dependency at a much older version, i.e. >=12.2.0,<13.0.0. Is there any reason for staying a whole year behind? Could this be bumped?
Thanks!