Open tmchartrand opened 1 year ago
mikejhuang
commented
7 months ago Please update your AllenSDK. The dependencies have been updated on AllenSDK with most of the version constraints to be unpinned. This should allow for much broader compatibility.
tmchartrand
commented
7 months ago Great to hear, thanks for the update!
From: Mike Huang @.> Sent: Wednesday, December 13, 2023 10:46 AM To: AllenInstitute/AllenSDK @.> Cc: Tom Chartrand @.>; Author @.> Subject: Re: [AllenInstitute/AllenSDK] Split core modules into new repository with minimal dependencies (Issue #2585)
Please update your AllenSDK. The dependencies have been updated on AllenSDK with most of the version constraints to be unpinned. This should allow for much broader compatibility.
— Reply to this email directly, view it on GitHubhttps://github.com/AllenInstitute/AllenSDK/issues/2585#issuecomment-1854523805, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADB2IIDARARLG3SWVX4JR33YJHZZ3AVCNFSM6AAAAAARPPGOV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGUZDGOBQGU. You are receiving this because you authored the thread.Message ID: @.***>
Describe the use case that is addressed by this feature. It's currently impossible to simply PIP install IPFX due to complex dependency conflicts between IPFX and AllenSDK. The actual portions of AllenSDK used by IPFX are quite minimal, and could easily be split into a bare-bones "AIBS internal tools" package.
Describe the solution you'd like Identify the submodules that are true dependencies of IPFX and other internal python tools (sending out a survey to owners of various repos might be the easiest way), and break those components out into a new repo/package with minimal dependencies.
Describe alternatives you've considered Actually tracking and matching dependencies between AllenSDK and other internal tools would be possible, but extremely challenging
Additional context
Do you want to work on this issue? Sorry, no time now.