tox-poetry-installer crashes due to import error

[finswimmer]

Hey,

we released poetry1.2.0 and poetry-core 1.1.0 today 🎉 Unfortunately this breaks tox-poetry-installer due to changed import paths.

Most of them can be fixed easily:

tox-poetry-installer/tox_poetry_installer/installer.py

Line 12 in b3a5e86

from poetry.core.packages import Package as PoetryPackage

from poetry.core.packages.package import Package as PoetryPackage 

and

tox-poetry-installer/tox_poetry_installer/utilities.py

Lines 13 to 14 in b3a5e86

	from poetry.core.packages import Dependency as PoetryDependency
	from poetry.core.packages import Package as PoetryPackage

from poetry.core.packages.dependency import Dependency as PoetryDependency
from poetry.core.packages.package import Package as PoetryPackage

But I'm not sure what's the best way to fix

tox-poetry-installer/tox_poetry_installer/_poetry.py

Line 33 in b3a5e86

from poetry.io.null_io import NullIO

This is not available anymore in poetry 1.2.0. Instead it's available in the most recent version of cleo:

from cleo.io.null_io import NullIO

While the easy changes are compatible with poetry < 1.2, the change of NullIO import isn't. Maybe just put another try/except in here to find put what's available?

fin swimmer

[enpaul]

Thanks for the report @finswimmer

I've just released version 0.8.5 which pins the Poetry requirement at less than 1.2 to back stop this issue in the immediate time frame. @Callek has a PR up to add support for Poetry 1.2 that I'll be looking at next to hopefully get this functionality added soon

[Callek]

Thanks for the report @finswimmer

I've just released version 0.8.5 which pins the Poetry requirement at less than 1.2 to back stop this issue in the immediate time frame. @Callek has a PR up to add support for Poetry 1.2 that I'll be looking at next to hopefully get this functionality added soon

My pr pins to an alpha of poetry 1.2, but happy to bump that to the final release depending on Ethan's opinion here.

Mostly just blocked on his time

[enpaul]

This issue should now be resolved by #70 , thanks to @Callek