ISOLDE's ToolShed entry broken

[Tristan Croll]

I'm afraid I just broke ISOLDE's ToolShed entry by uploading a bundle with a version string it doesn't like (1.0b5.1). Going to ​https://cxtoolshed.rbvi.ucsf.edu/apps/chimeraxisolde now just gives me a traceback page with InvalidVersion.

(a) Could you delete the offending bundle?

(b) What would be an acceptable version string? 1.0b5.post1 looks like the most PEP 440 compliant option? I know it's discouraged, but I'd like to stick with the current system of "new ISOLDE beta goes with new ChimeraX numeric version".

[Greg Couch]

Greg is managing the toolshed now with help from Conrad.

[Greg Couch]

The 1.0b5.1 has been removed. Will change bundle submission code to require that the version be legal.

FYI, pip doesn't like prereleases that much, by default they are not found when pip is searching for dependencies. So for the versions of ISOLDE that are matched to ChimeraX releases, it would be best if you dropped the beta suffix.

[Tristan Croll]

I've been trying to avoid taking the plunge to ISOLDE 1.0 until ChimeraX 
does (would seem strange to have a plugin that's 1.0 when the platform 
isn't). Perhaps I should have just stuck with 0.x.y, but I suppose it's 
too late now. Not sure if it's so important, though? ISOLDE isn't a 
dependency for anything else (yet), and the Clipper bundle that ISOLDE 
depends on *is* still on a 0.x.y scheme.

On 2020-04-16 17:02, ChimeraX wrote:

[Greg Couch]

Bundles will now be rejected when submitted if it has an invalid version number.

And "devel build" and "devel install" won't build the bundle in the first place if the version is invalid.