Changes between Initial Version and Version 1 of Ticket #5157, comment 5


Ignore:
Timestamp:
Oct 12, 2021, 2:19:22 PM (4 years ago)
Author:
Tom Goddard

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5157, comment 5

    initial v1  
    1 {{{
     1
    22Hi Greg,
    33
    … …  
    77Kind regards,
    88Ilse
    9 
    10 -----Oorspronkelijk bericht-----
    11 Van: ChimeraX <ChimeraX-bugs-admin@cgl.ucsf.edu>
    12 Verzonden: 29 September 2021 08:48
    13 CC: chimera-programmers@cgl.ucsf.edu; gregc@cgl.ucsf.edu; Lagerwaard, I.M. (Ilse) <i.m.lagerwaard@students.uu.nl>
    14 Onderwerp: Re: [ChimeraX] #5157: PyPi dependency not installed by "devel install"
    15 
    16 #5157: PyPi dependency not installed by "devel install"
    17 ---------------------------------------+------------------------
    18           Reporter:  i.m.lagerwaard@…  |      Owner:  Greg Couch
    19               Type:  defect            |     Status:  assigned
    20           Priority:  normal            |  Milestone:  1.4
    21          Component:  Tool Shed         |    Version:
    22         Resolution:                    |   Keywords:
    23         Blocked By:                    |   Blocking:
    24 Notify when closed:                    |   Platform:  all
    25            Project:  ChimeraX          |
    26 ---------------------------------------+------------------------
    27 Changes (by Greg Couch):
    28 
    29  * milestone:  1.3 => 1.4
    30 
    31 
    32 Comment:
    33 
    34  This bug is a side-effect of using "pip install --force-reinstall --no-  deps" to reinstall a bundle with the exact same version.  "--no-deps" is  needed to prevent other Python packages from upgrading to the latest  version in pypi.
    35 
    36  One workaround is to increase the version number of your bundle.  That is  needed anyway because you've added a dependency.  If the version number is  different, then "pip install --upgrade-strategy only-if-needed" is used,  and the dependency will be installed.
    37 
    38  Another workaround is to remove the bundle first, as mentioned previously.
    39  That way the normal install arguments are given to pip and the dependency  will be installed.  The disadvantage of doing the uninstall first is that  if the install fails for any reason, then the package is gone, and could  potentially leave ChimeraX unrunnable.  Nevertheless, I will put this  workaround into the daily build after the branch for 1.3 is made, so it  will either show up in 1.4 or we'll have confirmed that it isn't safe all  of the time.
    40 
    41  In the interim, I'll work on adding a toolshed command that installs a  package from pypi. Ticket #4762.
    42 
    43 --
    44 Ticket URL: <https://www.rbvi.ucsf.edu/trac/ChimeraX/ticket/5157#comment:4>
    45 ChimeraX <https://www.rbvi.ucsf.edu/chimerax/>
    46 ChimeraX Issue Tracker
    47 }}}