example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports data structures, or boltons has generally. Major areas addressed include: • packaging: package versioning, with a clean and less invasive alternative to versioneer • entity: robust base class for type-enforced

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. Supported version strings Conda supports to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our

example, <=1.0 matches 0.9, 0.9.1, and 1.0, but not 1.0.1. == and != are exact equality. Pre-release versioning is also supported such that >1.0b4 will match 1.0b5 and 1.0rc1 but not 1.0b4 or 1.0a5. EXAMPLE: followed by ! - can precede the actual version string (this is useful to indicate a change in the versioning scheme itself). Version comparison is case-insensitive. 88 Chapter 4. Contributors welcome conda to the CalVer versioning system as agreed upon in CEP 8 (Conda Enhancement Proposal). Please read that CEP for more information, but here is a quick synopsis. We hope that this versioning system and our