Conda 24.9.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the Release 24.9.3.dev1 • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 799 页 | 5.26 MB | 8 月前3
Conda 25.1.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the Release 25.1.2.dev1 • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 822 页 | 5.20 MB | 8 月前3
Conda 24.11.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the 24.11.3.dev2 • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 818 页 | 5.21 MB | 8 月前3
Conda 23.7.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 795 页 | 4.91 MB | 8 月前3
Conda 23.10.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 773 页 | 5.05 MB | 8 月前3
Conda 24.1.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 795 页 | 4.73 MB | 8 月前3
Conda 23.9.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 753 页 | 4.86 MB | 8 月前3
Conda 23.11.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 781 页 | 4.79 MB | 8 月前3
Conda 24.3.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 786 页 | 4.98 MB | 8 月前3
Conda 24.4.x Documentationare designed only for human read- ability and conda never parses them. build_number integer A non-negative integer representing the build number of the package. Unlike the build string, the build_number consecutive dots, a leading/trailing underscore) are not permitted. An optional epoch number - an integer followed by ! - can precede the actual version string (this is useful to indicate a change in the other types. • If a subcomponent has no correspondent, the missing correspondent is treated as integer 0 to ensure '1.1' == 1.1.0'. The resulting order is: 0.4 < 0.4.0 < 0.4.1.rc == 0.4.1.RC # case-insensitive0 码力 | 786 页 | 4.99 MB | 8 月前3
共 16 条
- 1
- 2













