works for me (on Linux):
$ sage -bt src/sage/game_theory
python -u setup.py install
Updating Cython code....
Enabling Cython debugging support
Finished Cythonizing, time: 2.55 seconds.
Discovering Python source code....
Discovered Python source, time: 0.02 seconds.
Cleaning up stale installed files....
- cleaning /home/dima/software/sage/local/lib/python2.7/site-packages
- cleaning /home/dima/software/sage/local/lib/site-python
- cleaning /home/dima/software/sage/src/build/lib.linux-x86_64-2.7
Finished cleaning, time: 0.08 seconds.
running install
running build
running build_py
running build_ext
warning: Replacing library search directory in linker command:
"/home/dima/software/sage.6.6/sage/local/lib" ->
"/home/dima/software/sage/local/lib"
Executing 0 commands (using 1 thread)
Time to execute 0 commands: 0.11 seconds.
Total time spent compiling C/C++ extensions: 0.14 seconds.
running install_lib
running install_data
running install_egg_info
Removing
/home/dima/software/sage/local/lib/python2.7/site-packages/sage-6.8.beta7-py2.7.egg-info
Writing
/home/dima/software/sage/local/lib/python2.7/site-packages/sage-6.8.beta7-py2.7.egg-info
Running doctests with ID 2015-07-04-22-41-59-36f0d948.
Git branch: newdownload
Using
--optional=database_gap,gap_packages,gcc,gmp,lidia,lrslib,mpir,openssl,python2,sage,scons
Doctesting 10 files.
sage -t --warn-long 73.0 src/sage/game_theory/__init__.py
[0 tests, 0.00 s]
sage -t --warn-long 73.0 src/sage/game_theory/all.py
[0 tests, 0.00 s]
sage -t --warn-long 73.0 src/sage/game_theory/cooperative_game.py
[101 tests, 0.66 s]
sage -t --warn-long 73.0 src/sage/game_theory/catalog_normal_form_games.py
[99 tests, 0.36 s]
sage -t --warn-long 73.0 src/sage/game_theory/catalog.py
[0 tests, 0.00 s]
sage -t --warn-long 73.0 src/sage/game_theory/parser.py
[58 tests, 0.09 s]
sage -t --warn-long 73.0 src/sage/game_theory/named_games.py
[0 tests, 0.00 s]
sage -t --warn-long 73.0 src/sage/game_theory/normal_form_game.py
[357 tests, 1.80 s]
sage -t --warn-long 73.0 src/sage/game_theory/gambit_docs.py
[0 tests, 0.00 s]
sage -t --warn-long 73.0 src/sage/game_theory/matching_game.py
[305 tests, 2.17 s]
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
post complete log; perhaps you have dodgy packages installed?
On Saturday, 4 July 2015 22:19:59 UTC+1, Vincent Knight wrote:
>
> Apologies if I'm missing something and this has been reported before.
>
> `./sage -bt src/sage/game_theory` and `sage -bt --optional=all
> src/sage/game_theory` both give:
>
> ```
> ...
> Git branch: develop
> Doctesting 10 files.
> Traceback (most recent call last):
> File "/Users/vince/sage/src/bin/sage-runtests", line 88, in <module>
> err = DC.run()
> File
> "/Users/vince/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
>
>
> line 1038, in run
> self.run_doctests()
> File
> "/Users/vince/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
>
>
> line 759, in run_doctests
> self.dispatcher = DocTestDispatcher(self)
> File
> "/Users/vince/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>
> line 1376, in __init__
> init_sage()
> File
> "/Users/vince/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>
> line 125, in init_sage
> from sympy.printing.pretty.stringpict import stringPict
> ImportError: No module named sympy.printing.pretty.stringpict
> ```
>
> Mac OSX.
>
> Apologies also if I'm missing details that could be helpful.
>
> Vince
>
>
> On 4 July 2015 at 22:13, Dima Pasechnik <dim...@gmail.com <javascript:>>
> wrote:
> >
> >
> > On Saturday, 4 July 2015 21:02:58 UTC+1, Nathann Cohen wrote:
> >>
> >> Helloooooo !
> >>
> >> > It looks like I have a stale list of (pseudo)packages - perhaps each
> >> > call to
> >> > "sage -i blah" duly puts "blah" on the list ?!
> >>
> >> It seems to be something like that: the message that you see which
> >> reports which packages may have 'failed to build' is generated by the
> >> script build/install.
> >>
> >> How do you think is guesses which packages failed to build? Well, it
> >> looks for log files which contain the word "error" (line 502 of
> >> build/install).
> >>
> >> So if you have a file in SAGE_LOGS/ which contains the word 'error',
> >> it will appear on that list.
> >>
> >> And you do not want to see mine, it is incredibly long.
> >
> >
> >
> > should the script check whether these packages are real Sage packages,
> and
> > dub these that are not there
> > "custom" packages? Otherwise it's very confusing...
> >
> > So the question is where to look for these lists...
> >
> >>
> >> Nathann
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "sage-release" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to sage-release...@googlegroups.com <javascript:>.
> > To post to this group, send email to sage-r...@googlegroups.com
> <javascript:>.
> > Visit this group at http://groups.google.com/group/sage-release.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Dr Vincent Knight
> Cardiff School of Mathematics
> Senghennydd Road,
> Cardiff
> CF24 4AG
> (+44) 29 2087 5548
> www.vincent-knight.com
> +Vincent Knight
> @drvinceknight
> Skype: drvinceknight
>
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
