Fix #113: Refactor getSitePackagesPath to use python discovery

[rvodden]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• All static analysis checks passed.
• This pull request is on the dev branch.
• I used gofmt for formatting the code before submitting the pull request.

---

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[rvodden]

I have read the CLA Document and I hereby sign the CLA

[talarian1]

Hi @rvodden, thanks a lot for your contribution.
I suggest we will wait with those changes, as for Poetry 1.2 and above the file 'direct_url.json' is not created anymore.
You can see this discussion for more details.
The only usage for the getSitePackagesPath logic is getting those files.
Sorry for the inconvenience and thanks again!

[talarian1]

Suggested change

	siteCmd := utils.NewCommand("poetry", "run", []string{"python", "-c", "import sysconfig; print(sysconfig.get_paths()['purelib']])"})
	siteCmd := utils.NewCommand("poetry", "run", []string{"python", "-c", "import sysconfig; print(sysconfig.get_paths()['purelib'])"})

[rvodden]

Hi @rvodden, thanks a lot for your contribution.
I suggest we will wait with those changes, as for Poetry 1.2 and above the file 'direct_url.json' is not created anymore.
You can see this discussion for more details.
The only usage for the getSitePackagesPath logic is getting those files.
Sorry for the inconvenience and thanks again!

aha great! I must admit i was thinking of authoring a poetry plugin which would output buildinfo... would that be interesting as an alternative to having to install jf-cli ?

[talarian1]

Thanks again for your interest in this, and for your effort.
I'm closing this for now, as we discussed here we will need a new implementation to solve this issue.