Python full version in pipfile

[jerempy]

Thank you for contributing to Pipenv!

The issue

#5345

A user requested that when the full version is specified that it gets added to a new pipfile when it is created so that he/she wouldn't need to manually add it themselves.

The fix

Found the spot where the pipefile [requires] section gets created and modified it slightly to save based on if full version was specified or not.

The checklist

• Associated issue
• A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

[oz123]

Thank you for your PR.

Please fix the linting issue, and add a news fragment.

This is then good to be merged!

[jerempy]

thanks @oz123 ! we should be good to go now 😎

[oz123]

Please rename the news snippet to: 5345.behavior.rst

[oz123]

As I suspected this change leads to breakage of CI.

Successfully set up CPython (3.7.14)

I think that pinning to a minor version is not a good thing. Unless it's additional. What I mean is, we should have both, e.g.:

python_version=3.7
python_full_verison=3.7.14

[jerempy]

@oz123 I updated it so now the pipfile will record both the python version and the full version in addition if specified. Also updated tests so should work for whatever python version the test is running. Sorry for the back and forth and hopefully we good to go now 🤞

[oz123]

OK. Already very promising. Just add some more explanation to the news file, and we are good to go.

[matteius]

What happens if a new minor version is released? Will users have to manually update the python_full_version?
EDIT: Ah -- nevermind -- I see it only populates this if a full version is specified.