#general
- b
bored-art-40741
05/06/2016, 7:52 PMI think pre is what we want - b
bored-art-40741
05/06/2016, 7:53 PMSo we'd want
I think1.1a0 - m
mammoth-pharmacist-54215
05/06/2016, 7:54 PMwhy not 1.1.0-pre1 - m
mammoth-pharmacist-54215
05/06/2016, 7:54 PMthat more closely follows our current convention - b
bored-art-40741
05/06/2016, 7:54 PMJust reading the pep - b
bored-art-40741
05/06/2016, 7:54 PMoh okay - b
bored-art-40741
05/06/2016, 7:54 PMCopy codePre-release spelling Pre-releases allow the additional spellings of alpha , beta , c , pre , and preview for a , b , rc , rc , and rc respectively. This allows versions such as 1.1alpha1 , 1.1beta2 , or 1.1c3 which normalize to 1.1a1 , 1.1b2 , and 1.1rc3 . In every case the additional spelling should be considered equivalent to their normal forms. - b
bored-art-40741
05/06/2016, 7:55 PMso it'd be1.1pre0 - l
limited-country-20626
05/06/2016, 7:55 PMdo we want to normalize against the existing spec we used for 1.0? so
?1.1-pre0 - m
mammoth-pharmacist-54215
05/06/2016, 7:55 PMthe pep allows for seperators: Pre-release separators Pre-releases should allow a . , - , or _ separator between the release segment and the pre-release segment. The normal form for this is without a separator. This allows versions such as 1.1.a1 or 1.1-a1 which would be normalized to 1.1a1 . It should also allow a seperator to be used between the pre-release signifier and the numeral. This allows versions such as 1.0a.1 which would be normalized to 1.0a1 . - m
mammoth-pharmacist-54215
05/06/2016, 7:55 PMwhich we use in the rc’s currently - l
limited-country-20626
05/06/2016, 7:56 PMI know that we parse these by regexs in places - b
bored-art-40741
05/06/2016, 7:56 PMAh you're right - b
bored-art-40741
05/06/2016, 7:56 PM
then?1.1-pre0 - m
mammoth-pharmacist-54215
05/06/2016, 7:56 PMfwiw as long as pypi handles it correctly I would prefer 1.1.0-pre1 - b
bored-art-40741
05/06/2016, 7:57 PMOr I suppose
is fine too1.1.0-pre0 - b
bored-art-40741
05/06/2016, 7:57 PMI agree - b
bored-art-40741
05/06/2016, 7:57 PMShould we start at 0 or 1? - b
bored-art-40741
05/06/2016, 7:57 PMEverything else is 0 indexed - m
mammoth-pharmacist-54215
05/06/2016, 7:57 PMhehe fine with pre0 vs pre1 … that part doesn’t matter to me as long as we are consistent - l
limited-country-20626
05/06/2016, 7:57 PMsure - matt would you send your proposal to pants-devel? - l
limited-country-20626
05/06/2016, 7:57 PMthen I will cut the release based on the general acceptance - m
mammoth-pharmacist-54215
05/06/2016, 7:58 PMsure, @limited-country-20626 would you mind doing a quick test on pypi to verify we aren’t crazy and things behave sanely? - l
limited-country-20626
05/06/2016, 8:00 PMhmmm...yeah although this is perhaps should be part of our publishing testing. I will try a little POC locally for now - m
mammoth-pharmacist-54215
05/06/2016, 8:01 PMI just mean by creating a package, bumping the version and then seeing if what you fetch from pypi is what you expect and not the pre-release version - m
mammoth-pharmacist-54215
05/06/2016, 8:01 PMnot actual pants… but some test project - m
mammoth-pharmacist-54215
05/06/2016, 8:03 PMemail sent - l
limited-country-20626
05/06/2016, 8:05 PMi understood - m
mammoth-pharmacist-54215
05/06/2016, 8:12 PMokay, let me know if you would rather I take it. pypi behaved for rc so I would be very surprised if pre caused problems - l
limited-country-20626
05/06/2016, 8:12 PMso what constraints are you specifically want to check? That a pip install pulls down a 1.0.0 even if a 1.0.1-pre0 is pushed?