Changes between Version 1 and Version 2 of Ticket #3898, comment 7


Ignore:
Timestamp:
Nov 2, 2020, 10:30:29 PM (5 years ago)
Author:
Greg Couch

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3898, comment 7

    v1 v2  
    1 Adding the Python >= 3.8 requirement catches errors at bundle installation time instead of runtime.  If the developer is super careful and checks that their code works with earlier versions of Python, then they can attest to that in their bundle_info.xml file.  But if the developer is lazy and just tests with the current version of ChimeraX, then the bundle is generated as being dependent on that version.  Your solution of building hkcage with an earlier version of ChimeraX is the right solution -- it is the same solution we use for binary compatibility on Linux.  In general, building on an older version is forwards compatible, and building on a new version is not backwards compatible.
     1Adding the Python >= 3.8 requirement catches errors at bundle installation time instead of runtime.  If the developer is super careful and checks that their code works with earlier versions of Python, then they can attest to that in their bundle_info.xml file.  But if the developer is "lazy" and just tests with the current version of ChimeraX, then the bundle is generated as being dependent on that version.  Your solution of building hkcage with an earlier version of ChimeraX is the right solution -- it is the same solution we use for binary compatibility on Linux.  In general, building on an older version is forwards compatible, and building on a new version is not backwards compatible.
    22
    33Should Python 3.8 bundles be listed as being available for ChimeraX 1.1?  No, they shouldn't, but that is a separate problem where the toolshed needs to infer or be given additional information to figure it out.