Fixing Python virtualenv in development

[anshikavashistha]

This is with reference to the issue

[softwarefactory-project-zuul]

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
https://fedora.softwarefactory-project.io/zuul/buildset/ad6469d08570488aae8a7b296922319d

❌ fi-tox-mypy FAILURE in 5m 17s
✔️ fi-tox-lint SUCCESS in 5m 13s
✔️ fi-tox-format SUCCESS in 4m 56s
❌ fi-tox-python38 FAILURE in 6m 49s
❌ fi-tox-python39 FAILURE in 6m 12s
❌ fi-tox-python310 FAILURE in 6m 52s
❌ fi-tox-python311 FAILURE in 6m 14s
❌ fi-tox-docs FAILURE in 6m 32s
✔️ fi-tox-bandit SUCCESS in 5m 02s
❌ fi-tox-diff-cover FAILURE in 7m 05s

[Zlopez]

@anshikavashistha Plenty of tests started failing after the change, could you look into that?

[anshikavashistha]

@Zlopez I am also trying to figure it out. Meanwhile you could suggest me the required modifications to be done.
I am currently to running all these tests which are getting failed.

[Zlopez]

If you look at the failing tests the issue is obvious anitya_version doesn't have get_distribution method.

[anshikavashistha]

@Zlopez How should I solved the failure if anitya_version doesn't have get_distribution method?

[Zlopez]

It's just the string that contains the same information as pkg_resources.get_distribution.

[anshikavashistha]

@Zlopez I agree with you. Yes that's right pkg_resources has get_ditsribution method but anitya_version don't have.
What should be the alternative to this method for anitya_version?

[anshikavashistha]

@Zlopez May be this will work version = version_str ?

[Zlopez]

anitya_version should be the same as what is returned by pkg_resources.get_distribution('anitya').version. But it needs to be tested first. I'm not sure if we already used poetry at the time this ticket was open. Just try it and see.

[anshikavashistha]

Sure @Zlopez I try it and tests it

[softwarefactory-project-zuul]

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
https://fedora.softwarefactory-project.io/zuul/buildset/239eaa5e45c24bde846c8f5f74a0ba8c

✔️ fi-tox-mypy SUCCESS in 5m 22s
✔️ fi-tox-lint SUCCESS in 4m 56s
❌ fi-tox-format FAILURE in 5m 07s
✔️ fi-tox-python38 SUCCESS in 8m 59s
✔️ fi-tox-python39 SUCCESS in 9m 24s
✔️ fi-tox-python310 SUCCESS in 9m 01s
✔️ fi-tox-python311 SUCCESS in 9m 01s
✔️ fi-tox-docs SUCCESS in 6m 28s
✔️ fi-tox-bandit SUCCESS in 5m 06s
✔️ fi-tox-diff-cover SUCCESS in 9m 07s

[softwarefactory-project-zuul]

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
https://fedora.softwarefactory-project.io/zuul/buildset/671d0fe790b74fb0b4127330dfba4a92

✔️ fi-tox-mypy SUCCESS in 5m 07s
✔️ fi-tox-lint SUCCESS in 4m 29s
❌ fi-tox-format FAILURE in 4m 24s
✔️ fi-tox-python38 SUCCESS in 8m 25s
✔️ fi-tox-python39 SUCCESS in 8m 47s
✔️ fi-tox-python310 SUCCESS in 9m 23s
✔️ fi-tox-python311 SUCCESS in 8m 23s
✔️ fi-tox-docs SUCCESS in 6m 22s
✔️ fi-tox-bandit SUCCESS in 5m 01s
✔️ fi-tox-diff-cover SUCCESS in 9m 23s

[anshikavashistha]

@Zlopez I have tried to test and run anitya_version .Here some of the tests are successful but one of them tox-format is not running.

[Zlopez]

And what was the output, did it returned the same value as pkg_resources.get_distribution('anitya').version?

The format should be easily fixed by running black on the code. Look at the documentation.

[anshikavashistha]

@Zlopez Sure I will try to format the code as mentioned in the documentation and then try to run

[softwarefactory-project-zuul]

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci
https://fedora.softwarefactory-project.io/zuul/buildset/a9b1a722b7c246d7b3612a7d87a4818b

✔️ fi-tox-mypy SUCCESS in 5m 08s
✔️ fi-tox-lint SUCCESS in 5m 05s
❌ fi-tox-format FAILURE in 4m 45s
✔️ fi-tox-python38 SUCCESS in 8m 58s
✔️ fi-tox-python39 SUCCESS in 9m 20s
✔️ fi-tox-python310 SUCCESS in 9m 16s
✔️ fi-tox-python311 SUCCESS in 8m 56s
✔️ fi-tox-docs SUCCESS in 6m 35s
✔️ fi-tox-bandit SUCCESS in 5m 09s
✔️ fi-tox-diff-cover SUCCESS in 10m 05s