[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#896289: marked as done (python-sagetex: sagetex fails to import)

Your message dated Sat, 5 Jan 2019 18:01:58 +0400
with message-id <b4698660-371b-e80a-a6d5-4f10169a46e0@rezozer.net>
and subject line python-sagetex: sagetex fails to import
has caused the Debian Bug report #896289,
regarding python-sagetex: sagetex fails to import
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
896289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896289
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: python-sagetex
Version: 3.0+ds-6
Severity: serious
User: helmutg@debian.org
Usertags: python-import

After installing python-sagetex importing the module sagetex
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/sagetex.py", line 31, in <module>
    from sage.misc.latex import latex
  File "/usr/lib/python2.7/dist-packages/sage/misc/latex.py", line 67, in <module>
    from sage.misc.cachefunc import cached_function, cached_method
  File "sage/misc/function_mangling.pxd", line 1, in init sage.misc.cachefunc
  File "sage/misc/function_mangling.pyx", line 41, in init sage.misc.function_mangling
  File "/usr/lib/python2.7/dist-packages/sage/misc/sageinspect.py", line 129, in <module>
    from sage.env import SAGE_SRC
  File "/usr/lib/python2.7/dist-packages/sage/env.py", line 123, in <module>
    _add_variable_or_fallback('SAGE_ETC',        opj('$SAGE_LOCAL', 'etc'))
  File "/usr/lib/python2.7/dist-packages/sage/env.py", line 103, in _add_variable_or_fallback
    value = sep.join(components)
TypeError: sequence item 0: expected string, NoneType found
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.7/dist-packages/sage/misc/temporary_file.py", line 51, in delete_tmpfiles
    from sage.misc.misc import SAGE_TMP
  File "/usr/lib/python2.7/dist-packages/sage/misc/misc.py", line 53, in <module>
    from sage.env import DOT_SAGE, HOSTNAME
  File "/usr/lib/python2.7/dist-packages/sage/env.py", line 123, in <module>
    _add_variable_or_fallback('SAGE_ETC',        opj('$SAGE_LOCAL', 'etc'))
  File "/usr/lib/python2.7/dist-packages/sage/env.py", line 103, in _add_variable_or_fallback
    value = sep.join(components)
TypeError: sequence item 0: expected string, NoneType found
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.7/dist-packages/sage/misc/temporary_file.py", line 51, in delete_tmpfiles
    from sage.misc.misc import SAGE_TMP
  File "/usr/lib/python2.7/dist-packages/sage/misc/misc.py", line 53, in <module>
    from sage.env import DOT_SAGE, HOSTNAME
  File "/usr/lib/python2.7/dist-packages/sage/env.py", line 123, in <module>
    _add_variable_or_fallback('SAGE_ETC',        opj('$SAGE_LOCAL', 'etc'))
  File "/usr/lib/python2.7/dist-packages/sage/env.py", line 103, in _add_variable_or_fallback
    value = sep.join(components)
TypeError: sequence item 0: expected string, NoneType found

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut

--- End Message ---
--- Begin Message --- 
Hello SageMath and TeX enthusiasts !

My current understanding is that SageTex is before all a LaTeX package
that uses SageMath behind the scene.

From ``The SageTeX package'' manual (distributed in sagetex-doc),
at the beginning of the section ``Usage'', we read:

  Let’s begin with a rough description of how SageTEX works. Naturally the very
  first step is to put \usepackage{sagetex} in the preamble of your document.
  When you use macros from this package and run LaTeX on your file, along with
  the usual zoo of auxiliary files, a .sage file is written with the same basename as
  your document. This is a Sage source file that uses the Python module from this
  package and when you run Sage on that file, it will produce a .sout and a .scmd file.

This a common operative fashion in the [La]TeX realm; see bibtex(1) or makeindex(1) for example.

Accodingly, I am closing the bugreport.

Cheers,
Jerome

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calculus@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: