Hi Bianca,
The ".taskslab11419" section of your version name doesn't meet the requirements for version numbers described in https://www.python.org/dev/peps/pep-0440/#public-version-identifiers, as the only non-numeric text elements permitted are "a" (alpha releases), "b" (beta releases), "c" (release candidates), "dev" (dev releases), and "post" (post-releases).
The simplest resolution would be to drop the ".taskslab11419" section, and just make the version 0.2.0 instead. Alternatively, if keeping the number is important, you could make a dev release (0.2.0.dev11419), or use a 4 segment version number (0.2.0.11419).
Cheers, Nick.
On Tue, 27 Apr 2021 at 14:01, Bianca Reyes biancamoniquereyes@gmail.com wrote:
Hi Nick and Donald,
I’m emailing you because I can’t seem to resolve an issue with my project wherein I try to install using pip command and it returns:
WARNING: Built wheel for SomeProject is invalid: Metadata 1.2 mandates PEP 440 version, but '0.2.0.taskslab11419' is not
Failed to build SomeProject
I’ve read your documentation with PEP 440 version but my version name *0.2.0.taskslab11419* does not seem to be invalid based on your documentation. Can you guys help me out here? I’ve been trying to fix this for almost a week now but to no avail.
Btw, I’m using python3.8 and pip 21.1 version.
Hoping to hear from you soon.
Thank you and cheers,
Bianca
Sent from Mail https://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient Virus-free. www.avg.com http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient <#m_3295279858084880915_m_7829119531011239564_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On 2021-04-27 20:32:07 +1000 (+1000), Nick Coghlan wrote: [...]
The simplest resolution would be to drop the ".taskslab11419" section, and just make the version 0.2.0 instead. Alternatively, if keeping the number is important, you could make a dev release (0.2.0.dev11419), or use a 4 segment version number (0.2.0.11419).
[...]
And yet another option is to record it in custom PEP 566 metadata at package build time. Modules like setuptools_scm and pbr use this to store Git commit identifiers and similar information so that programs can access the data at runtime (e.g. for annotating their version output).