Opened 5 years ago

Closed 4 years ago

#873 closed task (fixed)

Lower entry barrier for developers

Reported by: butler Owned by: GitHub <noreply@…>
Priority: major Milestone: Admin Tasks
Component: SasView Keywords:
Cc: Work Package: SasView Admin


Robert French has created a simple script to get SasView up and running on Macs. However, as commented by Paul Kienzle and Andrew Jackson the impact could be very significantly magnified if this effort could be expanded to be more general both for mac users as well as other platforms. There comments on that pull request will be entered as the first comment on this ticket.

Meanwhile really represents a renewed interest in ticket #219 which lists some work by Peter Parker on an Anaconda solution which was not finished before he left but is used by a number of people and which is I think one of Paul Kienzle's suggestions. Anybody working on this should consult that ticket which I am now going to close as obsolete without copying all the comments here (hence the link to it above)

Change History (4)

comment:1 Changed 5 years ago by butler

Comments extracted from pull request used to generate this ticket

From Paul Kienzle

Better yet, use brew create to generate sasview.rb and throw it into a sasview-homebrew repo so you can use brew tap sasview/sasview to locate and brew install sasview to install (according to the docs…haven't actually tried it). You can require hdf5, the wx libraries, and anything else we need as part sasview.rb, and add the pip install h5py Pillow wx … before the python install. The xcode-select —install should be part of the brew setup instructions; probably don't want it as part of the shell script.

Anaconda is another viable option which is a little less intrusive than brew (no sudo required, and doesn't interact with the system path). It also works with Linux and Windows.

The main point of a personal build is to allow users to run directly from the git repo and help improve sasview. With a few tweaks we could make it so that you can use /Applications/Sasview 4.x/python to run the development version with all the dependencies already available. A few more tweaks would give us a virtual python environment complete with pip in case users want to play with third-party packages in their sasview extensions.

From Andrew Jackson

This is great, but I agree with Paul on the fact that not all developers can use homebrew (I for instance like to keep my install as clean as I can and have multiple pythons via anaconda).

My only request here is to rename the script to clearly indicate this is a homebrew config, then it is fine to merge.

Please also then make a ticket in trac for making the brew repo as per Paul's request since that is probably the long term better approach.

comment:2 Changed 4 years ago by butler

  • Milestone changed from SasView 4.2.0 to Admin Tasks
  • Type changed from defect to task

comment:3 Changed 4 years ago by wojciech

Suggested solution. Anaconda + yml file

comment:4 Changed 4 years ago by GitHub <noreply@…>

  • Owner set to GitHub <noreply@…>
  • Resolution set to fixed
  • Status changed from new to closed

In 19e584b7c09f0e4a8011642c0b514de21b22a8c4/sasview:

Merge pull request #114 from SasView?/ticket-873

ticket-873 Lower entry barrier for new developers

closes #873

Note: See TracTickets for help on using tickets.