Relax astra-toolbox requirement to >=2.1?

[ericpre]

CIL currently supports astra-toolbox >=1.9.9.dev5,<=2.1. Would it be possible to use astra-toolbox 2.1 in etspy?

[AndrewHerzing]

I have used astra version 2.1.3 with no issues.

[jat255]

Great, I'll relax that requirement in the my upcoming PR

…

On Fri, Oct 25, 2024 at 12:52 PM Andrew Herzing ***@***.***> wrote: I have used astra version 2.1.3 with no issues. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJYCXLJMBPD23PEAF4CLIDZ5KHN7AVCNFSM6AAAAABQT2D7A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZYGU4DSMRVGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Joshua Taillon www.joshuataillon.com

[jat255]

@ericpre after some more investigation, downgrading this dependency causes some headaches on the packaging side of things due to certain versions of astra not being available on PyPI. I'm hopeful that this can be resolved by CIL updating to the latest astra toolbox version without too much trouble.

[ericpre]

Thank you @jat255. Maybe I should have be more specific, would it be possible to use astra-toolbox >=2.1 in the dependency requirement, so that CIL and etspy can be install in the same environment after CIL have been installed using conda packages.
The idea would be that etspy can be installed as follow:

• dependencies from pypi: astra-toolbox 2.2
• dependencies from conda-forge: astra-toolbox 2.1 (and CIL)

Relaxing dependencies requirement as much as possible is very useful and can avoid a lot of installation trouble.

[jat255]

I believe I've sorted this out, and one should now (after the conda packages are built) be able to install etspy alongside astra-toolbox 2.1.2 and numpy 1.26, which should allow for installation with CIL