Attempt to upgrade poetry version

[mariusvniekerk]

Attempt to upgrade our vendored poetry to latest

[netlify]

✅ Deploy Preview for conda-lock ready!

Name	Link
🔨 Latest commit	6937de0
🔍 Latest deploy log	https://app.netlify.com/sites/conda-lock/deploys/63bf373332d8dd000888e6bb
😎 Deploy Preview	https://deploy-preview-310--conda-lock.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[mariusvniekerk]

@maresb tried to run the vendoring helper, but it seems that it didn't replace the import paths appropriately.

Actually seems it didn't really run? Can't seem to run the reset

Cannot reset migration stage 8 when not on a migration commit

No idea what this means

[maresb]

Hi, sorry for the confusion.

The original vendoring procedure was quite complicated. My migration script was designed to run once, and only with that specific version of Poetry/Poetry Core/Cleo. (The idea was to implement it in code so that when it comes time to upgrade we know exactly what procedure was used, and we can make the appropriate changes.) Thus the migration named "Vendor Poetry" has already been applied.

The migrate-code reset command runs git reset to undo previously-applied migration commits, but this only works when HEAD is a migration commit.

Rather than add an EPOCH I'd suggest m = Migration("Upgrade poetry to v1.3.2").

Taking a quick look, seems that we need to change vendor_helpers.py line 104 to

            f"/{self.name.replace('-', '_')}-{self.version}.tar.gz"

and line 390 to

                {"python_version": python_version, "sys_platform": "linux"},

but then it's getting confused due to importlib_metadata having multiple python_version requirements. I'll try to look into this soon.