StephanieThanks!Looks like I might have to run a new copy of the install script.So running yt update --all did not work, unfortunately. It still gives me the error:ImportError: No module names write_array
On Wed, Aug 28, 2013 at 4:40 PM, Matthew Turk <email@example.com> wrote:
Looks to me like write_array is not accessible anymore, which is
breaking the "yt" command. (This is a problem we should address.) At
worst, you may need to re-run a new copy of the install script; you
can do this over top of the old one, or remove and start anew.
We have some packaging plans under way right now that will reduce the
importance of the install script and the "yt update" command. But
more on that as they are available!
On Wed, Aug 28, 2013 at 3:55 PM, Stephanie Tonnesen <firstname.lastname@example.org> wrote:
> Dear all,
> After a pretty long (few month) hiatus, I just tried to update my yt and
> seem to have broken it.
> Now my desktop is frozen so I can't cut and paste the long outputs, but it
> boils down to:
> The current version of the code is:
> 0be45301e0eb (yt) tip
> This version CAN be automatically updated.
> added 1740 changesets with 3520 changes to 355 files (+1 heads)
> Updating the repository
> 126 files updates, 0 files merged, 0 files removed, 0 files unresolved
> BROKEN: See /u/stonnes/Installs/yt-x86_64/src/yt-hg/yt_updater.log
> So I looked at that
> and the first thing it had was:
> pulling from https://bitbucket.org/yt_analysis/yt/
> (run 'hg update' to get a working copy)
> So I ran hg update and then it failed and said I had no module named
> When I start python2.7
> and type
>>> from yt.mods import *
> I get the same error (no module write_array)
> Any advice would be appreciated!
> yt-users mailing list
yt-users mailing list