Bug 422411 - Fail to create symbolic variables
Summary: Fail to create symbolic variables
Status: RESOLVED UPSTREAM
Alias: None
Product: cantor
Classification: Applications
Component: octave-backend (other bugs)
Version First Reported In: 20.04
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Cantor Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-03 09:48 UTC by heqromancer
Modified: 2020-06-05 12:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description heqromancer 2020-06-03 09:48:24 UTC
SUMMARY


STEPS TO REPRODUCE
1. Type the following entry
 
pkg load symbolic
syms x

2. Evaluate entry

OBSERVED RESULT

/usr/lib/python3.8/site-packages/sympy/__init__.py:672: SymPyDeprecationWarning: 

importing sympy.core.compatibility with 'from sympy import *' has been
deprecated since SymPy 1.6. Use import sympy.core.compatibility
instead. See https://github.com/sympy/sympy/issues/18245 for more
info.

  self.Warn(
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 12, in octoutput_drv
  File "<stdin>", line 54, in octoutput
  File "<stdin>", line 55, in octoutput
  File "/usr/lib/python3.8/site-packages/sympy/__init__.py", line 677, in __getattr__
    return getattr(self.mod, name)
AttributeError: module 'sympy.core.compatibility' has no attribute 'integer_types'


EXPECTED RESULT
It should define the variable.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.5
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
This has been working for me until a couple of days ago.
Comment 1 heqromancer 2020-06-03 09:55:27 UTC
It has also started failing on Octave.
(Perhaps I should move this report there?)
Comment 2 Nikita Sirgienko 2020-06-05 11:14:49 UTC
I don't think, that this is Cantor problems, because of your python trace the root of problem is Octave(Sage) itself.
As I see, you use Manjaro, right? Manjaro, as based on Arch Linux distributive, uses rolling release scheme - for providing latest program versions. So, I suppose, that your sympy packages have been updated recently, but without proper Octave (Sage) updates. It actually, typical problem of Manjaro - problems with packages like that (and the reason for stable distros like Ubuntu LTS to exists).
So, the problem is that, then you run `syms x` Octave (or Sage), as SymPy user, try to use attribute `integer_types` from `sympy.core.compatibility`, but the attribute was deleted since SymPy 1.6 , so Octave code for using sympy have failed and module can't be used, so symobolic variable can't be created.
I have recomend go to Octave/Sage bugtracker and report problem there, with this python trace message. Or you can just wait some days  - I don't think, that you are the only user of symbolic packages, so maybe the problem already reported and will solved in near future sage/octave packages updates.
Comment 3 heqromancer 2020-06-05 12:51:30 UTC
(In reply to Nikita Sirgienko from comment #2)
> I don't think, that this is Cantor problems, because of your python trace
> the root of problem is Octave(Sage) itself.
> As I see, you use Manjaro, right? Manjaro, as based on Arch Linux
> distributive, uses rolling release scheme - for providing latest program
> versions. So, I suppose, that your sympy packages have been updated
> recently, but without proper Octave (Sage) updates. It actually, typical
> problem of Manjaro - problems with packages like that (and the reason for
> stable distros like Ubuntu LTS to exists).
> So, the problem is that, then you run `syms x` Octave (or Sage), as SymPy
> user, try to use attribute `integer_types` from `sympy.core.compatibility`,
> but the attribute was deleted since SymPy 1.6 , so Octave code for using
> sympy have failed and module can't be used, so symobolic variable can't be
> created.
> I have recomend go to Octave/Sage bugtracker and report problem there, with
> this python trace message. Or you can just wait some days  - I don't think,
> that you are the only user of symbolic packages, so maybe the problem
> already reported and will solved in near future sage/octave packages updates.

Yes, it's already reported and confirmed in Octave.