Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#25401 closed defect (duplicate)

py3: fix maxima interface

Reported by: chapoton Owned by:
Priority: critical Milestone: sage-duplicate/invalid/wontfix
Component: python3 Keywords:
Cc: embray, jdemeyer, fbissey Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by chapoton)

that prevents sage-python3 8.3.b2 to start.

sage-python3 does no start anymore :

    575         self._prompt_wait = ([self._prompt.encode('ascii')] +
--> 576                              [re.compile(x) for x in self._ask] +
        global re.compile = <function compile at 0x7f7eb678c8c8>
        global x = undefined
        self._ask = [b'zero or nonzero\\?', b'an integer\\?', b'positive, negat\
ive or zero\\?', b'positive or negative\\?', b'positive or zero\\?', b'equal to\
    577                              [b'Break [0-9]+'])  # note that you might \
need to change _expect_expr if you
    578                                                  # change this
    579         self._error_re = re.compile('(Principal Value|debugmode|incorre\
ct syntax|Maxima encountered a Lisp error)')
    580         self._display2d = False
    582     def set_seed(self, seed=None):
    583         """
    585         make_random_state (n) returns a new random state object created\
 from an
    586         integer seed value equal to n modulo 2^32. n may be negative.
    588         EXAMPLES::
    590             sage: m = Maxima()
AttributeError: 'bytes' object has no attribute 'encode'

Change History (9)

comment:1 Changed 3 years ago by chapoton

  • Branch set to u/chapoton/25401
  • Commit set to abb8a44a61f1817ebb97e70da84fec55325cdd08
  • Status changed from new to needs_review

not really sure if this is the right fix. But I am quite annoyed that python3-sage does not start anymore...

New commits:

abb8a44make sage3 start again

comment:2 Changed 3 years ago by chapoton

  • Status changed from needs_review to needs_work

this does not fix the problem

comment:3 Changed 3 years ago by fbissey

For completeness can you paste the offending error in the description. I know where you posted in an another ticket but I'd rather not switch back and forth just to look at the problem.

comment:4 Changed 3 years ago by chapoton

  • Description modified (diff)

comment:5 Changed 3 years ago by chapoton

This seems to be handled correctly in #24269

comment:6 Changed 3 years ago by chapoton

  • Milestone changed from sage-8.3 to sage-duplicate/invalid/wontfix
  • Status changed from needs_work to positive_review

ok, let us close this one and work on #24269 instead

comment:7 Changed 3 years ago by chapoton

  • Authors Frédéric Chapoton deleted

comment:8 Changed 3 years ago by embray

  • Resolution set to duplicate
  • Status changed from positive_review to closed

comment:9 Changed 3 years ago by chapoton

  • Branch u/chapoton/25401 deleted
  • Commit abb8a44a61f1817ebb97e70da84fec55325cdd08 deleted
Note: See TracTickets for help on using tickets.