#```sql
1 messages · Page 1 of 1 (latest)
[{
"filename": "build-0.1.0-py2.py3-none-any.whl"
}, {
"filename": "build-0.0.2.tar.gz"
}, {
"filename": "build-0.0.3.1.tar.gz"
}, {
"filename": "build-0.0.4.tar.gz"
}, {
"filename": "build-0.0.4-py2.py3-none-any.whl"
}, {
"filename": "build-0.0.2-py2.py3-none-any.whl"
}, {
"filename": "build-0.0.3.1-py2.py3-none-any.whl"
}, {
"filename": "build-0.8.0-py3-none-any.whl"
}, {
"filename": "build-0.8.0.tar.gz"
}, {
"filename": "build-0.6.0.tar.gz"
}, {
"filename": "build-0.6.0-py3-none-any.whl"
}, {
"filename": "build-0.6.1.tar.gz"
}, {
"filename": "build-0.6.1-py3-none-any.whl"
}, {
"filename": "build-0.6.0.post1-py3-none-any.whl"
}, {
"filename": "build-0.6.0.post1.tar.gz"
}, {
"filename": "build-0.3.1.tar.gz"
}, {
"filename": "build-0.3.1-py2.py3-none-any.whl"
}, {
"filename": "build-0.3.1.post1-py2.py3-none-any.whl"
}, {
"filename": "build-0.3.1.post1.tar.gz"
}, {
"filename": "build-0.0.1-py2.py3-none-any.whl"
}, {
"filename": "build-0.4.0-py2.py3-none-any.whl"
}, {
"filename": "build-0.4.0.tar.gz"
}, {
"filename": "build-0.3.0.tar.gz"
}, {
"filename": "build-0.3.0-py2.py3-none-any.whl"
}, {
"filename": "build-0.7.0-py3-none-any.whl"
}, {
"filename": "build-0.7.0.tar.gz"
}, {
"filename": "build-0.9.0-py3-none-any.whl"
}, {
"filename": "build-0.9.0.tar.gz"
}, {
"filename": "build-0.2.0-py2.py3-none-any.whl"
}, {
"filename": "build-0.2.0.tar.gz"
}, {
"filename": "build-0.2.1.tar.gz"
}, {
"filename": "build-0.2.1-py2.py3-none-any.whl"
}, {
"filename": "build-0.1.0.tar.gz"
}, {
"filename": "build-1.0.0-py3-none-any.whl"
}, {
"filename": "build-1.0.0.tar.gz"
}, {
"filename": "build-0.0.1.tar.gz"
}, {
"filename": "build-0.10.0-py3-none-any.whl"
}, {
"filename": "build-0.10.0.tar.gz"
}, {
"filename": "build-0.5.0.tar.gz"
}, {
"filename": "build-0.5.0-py2.py3-none-any.whl"
}, {
"filename": "build-0.5.1-py2.py3-none-any.whl"
}, {
"filename": "build-0.5.1.tar.gz"
}]
hmm, looks like these are quite old and thus missing from the dataset:
id | name | version | action | submitted_date | submitted_by
---------+-------+---------+-------------------------------------------+---------------------+------------------
1668310 | build | 1.0.1 | new release | 2015-08-07 14:20:41 | benjamin.hodgson
1668311 | build | 1.0.1 | add source file build-1.0.1.zip | 2015-08-07 14:20:59 | benjamin.hodgson
1668312 | build | 1.0.1 | add 3.4 file build-1.0.1-py3-none-any.whl | 2015-08-07 14:21:01 | benjamin.hodgson
1668313 | build | 1.0.1 | add 3.4 file build-1.0.1-py3.4.egg | 2015-08-07 14:21:05 | benjamin.hodgson
Are there any other versions to watch out for? Or is it only 1.0.1?
Then I could just do 1.0.2 and we'd not have to worry about it again.
unfortunately that one has been used as well:
warehouse=> select action, submitted_date from journals where name='build' and action ilike 'add %';
action | submitted_date
---------------------------------------------------------+----------------------------
add Owner benjamin.hodgson | 2015-08-07 12:55:26
add source file build-1.0.zip | 2015-08-07 12:55:40
add 3.4 file build-1.0-py3.4.egg | 2015-08-07 12:55:44
add 3.4 file build-1.0-cp34-none-win32.whl | 2015-08-07 12:55:48
add source file build-1.0.1.zip | 2015-08-07 14:20:59
add 3.4 file build-1.0.1-py3-none-any.whl | 2015-08-07 14:21:01
add 3.4 file build-1.0.1-py3.4.egg | 2015-08-07 14:21:05
add source file build-1.0.2.zip | 2015-08-07 15:09:17
add 3.4 file build-1.0.2-py3.4.egg | 2015-08-07 15:09:25
add 3.4 file build-1.0.2-py3-none-any.whl | 2015-08-07 15:09:33
those are all the ones which would cause conflicts
you could also do a post release: https://peps.python.org/pep-0440/#post-releases
Python Enhancement Proposals (PEPs)
We can do post1 for 1.0.1 and 1.0.2 if there is one, 1.0.1.post1 was what I make a PR for.