The link between the js.* python package version identifier and the version attribute of Library instances yields three possibly confusing situations.
I am not sure what to do about these situations, but thought it better to mention them in the issues list:
- The :version: information in generated URLs may contain release-specific information:
If we add CDN information to js.jquery and we release this as version 1.4.4-1 (a packaging release), the URLs to the resources will contain 1.4.4-1 as their version identifier.
Shall we define version=1.4.4 in the Library instance in order to prevent this? We can still use 'hashing' for packages that are installed in development mode.
The ':version:1.4.4' identifier in the URL for jquery could be considered misleading, as requests for ':version:1.5.0' and ':version:1.4.3' will also return the contents of 1.4.4.
It is generally not possible to have two versions of a js package in the same interpreter. If someone really needs jquery.js 1.4 and 1.3 in different pages, he/she can create a Library and register it for the name 'jquery-1.3'.