You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release a new version of text_ls_core that doesn't depend on click #46
My project can't upgrade to black version 20.8b1 because of the latest published version of textx_ls_core depends on click version 7.0.
$ poetry update black
Updating dependencies
Resolving dependencies... (0.1s)
SolverProblemError
Because no versions of black match >20.8b1,<21.0
and black (20.8b1) depends on click (>=7.1.2), black (>=20.8b1,<21.0) requires click (>=7.1.2).
And because textx-ls-core (0.1.1) depends on click (7.0)
and no versions of textx-ls-core match >0.1.1,<0.2.0, black (>=20.8b1,<21.0) is incompatible with textx_ls_core (>=0.1.1,<0.2.0).
So, because tsdoc0 depends on both textx_ls_core (^0.1.1) and black (^20.8b1), version solving failed.
I really appreciate the message, @igordejanovic. And I'm sorry to pester because you probably have a lot on your plate. If there's any way you could find <10 minutes to run the PyPi publishing command sooner, I would be sooooo grateful. I'm under a lot of pressure to get all our codebase's dependencies ready for Python 3.10 ASAP.
I can feel your pain and will help if I can. It seems that click dependency removal has happened after v0.1.2 release, so a new release should be made. I'll try to investigate more during next week.
@ryansobol It seems that a new release is required. It is not a simple PyPI release command. It would require some cleanup. I don't have time to deal with it at the moment (probably will in a few weeks). I've contacted @danixeee. He is overbooked also. If you are in a hurry, the best workaround I could think of is for you to fork the project and do quick and dirty release under different name (please just make a note about that in README or somewhere visible). If you depend on regular releases that might be your best strategy. You can always pull upstream changes.
Activity
danixeee commentedon Nov 29, 2020
Sure, I'll release it tomorrow.
ryansobol commentedon Dec 7, 2020
Any news?
ryansobol commentedon Oct 15, 2021
@danixeee or @igordejanovic, would either of you please, please publish
text_ls_corev0.1.2 to PyPi? It's been almost 2 years since it was released on GitHub but never found its way to PyPi. I'm sure you both are super busy, but this simple act would really make a big difference to a code base that I maintain.igordejanovic commentedon Oct 15, 2021
Hi @ryansobol . I plan to put some time into textX-LS during next month. If @danixeee don't find time for a release until then I'll do the release.
ryansobol commentedon Oct 15, 2021
I really appreciate the message, @igordejanovic. And I'm sorry to pester because you probably have a lot on your plate. If there's any way you could find <10 minutes to run the PyPi publishing command sooner, I would be sooooo grateful. I'm under a lot of pressure to get all our codebase's dependencies ready for Python 3.10 ASAP.
igordejanovic commentedon Oct 16, 2021
I can feel your pain and will help if I can. It seems that click dependency removal has happened after v0.1.2 release, so a new release should be made. I'll try to investigate more during next week.
igordejanovic commentedon Oct 25, 2021
@ryansobol It seems that a new release is required. It is not a simple PyPI release command. It would require some cleanup. I don't have time to deal with it at the moment (probably will in a few weeks). I've contacted @danixeee. He is overbooked also. If you are in a hurry, the best workaround I could think of is for you to fork the project and do quick and dirty release under different name (please just make a note about that in README or somewhere visible). If you depend on regular releases that might be your best strategy. You can always pull upstream changes.