Failed to handle doesn't exist resource correctly about balanced-python

[fangpenlin]

What is this 1.1.0dev here? I cannot see this in our git history. Did I miss something?

cc @remear

[remear]

I'm not aware of any 1.1.0dev version. What version actually installed when you ran pip install balanced==1.1.0dev?

[fangpenlin]

@remear 1.1.0.dev will be installed

https://pypi.vandelay.io/balanced/prod/+simple/balanced/

[remear]

I don't know what's creating that.

[fangpenlin]

@remear That package affects acceptance testing in some scenarios.

rev1 develop-inst: /srv/acceptance
  /srv/acceptance$ /srv/acceptance/.tox/rev1/bin/pip install --pre -e /srv/acceptance >/srv/acceptance/.tox/rev1/log/rev1-2.log

Since tox command install with --pre argument by default. And if the our pypi is in use, that 1.1.0dev will be installed. Could you remove it if no body is using it?

[matthewfl]

1.1.0dev is the package that is in our own pypi server

see https://github.com/balanced/acceptance/pull/25#discussion_r11873841 for reference. We need to delete that package and then this error will go away

[remear]

This is not happening 1.0.1, the latest public release. Go ahead and delete 1.1.0dev. Closing this.

[mjallday]

I think the python package should be pinned to >1.0,<1.1 in the future. That allows us to follow the semver odd/even numbers for development - https://en.wikipedia.org/wiki/Software_versioning

This is something we've been practicing in the cookbooks tho we should tread carefully about publishing them to public package repos since we haven't mentioned this to our customers.

[matthewfl]

@mjallday I don't think that will help in this case since I am betting that 1.1.0dev < 1.1

[mjallday]

you're correct @matthewfl but if we stick to that convention we no longer need to append dev to any version numbers so that wouldn't be an issue.

[mahmoudimus]

@mjallday @remear @matthewfl this is very simple:

• do not tag on odd releases
• tag means you're releasing
• odd is always HEAD