Author Topic: Import Python fail  (Read 14016 times)

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Import Python fail
« on: March 08, 2024, 04:05:29 am »
I tried RE some Python source and EA croaked
Quote
There was an error parsing Z:\Documents\Geo\objdump.py  on line 21.  Unexpected symbol: :
where that line (and all the rest) run perfectly. Looks like this
Code: [Select]
with open(fn) as f:

On another file I got
Quote
There was an error parsing Z:\Documents\Geo\locator.py  on line 47.  Unexpected symbol: <<DEDENT>>
which in source is also perfectly (and running) code.

The mentioned files were only partially imported and I can do the rest manually. However: why??

I'm on 1558

q.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Import Python fail
« Reply #1 on: March 12, 2024, 02:42:27 am »
Actually I did not ecpect any response from Sparx. Sad though my expectation was met - again

q.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8063
  • Karma: +118/-20
    • View Profile
Re: Import Python fail
« Reply #2 on: March 12, 2024, 08:24:27 am »
I don't know if you actually reported this (I can't see it in the list of issues that are under investigation), but even when code engineering was my area I couldn't give a useful answer from this.

My only suggestion at the moment is to try 16.1.

Quote
Release Notes for 16.1 Build 1621
*********************************

Code Engineering
  Improve Code Engineering/Code Editor to support Python 3.9 and Python 3.10 new features

If that doesn't work, then I'd suggest submitting a file to support for investigation.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Import Python fail
« Reply #3 on: March 12, 2024, 10:15:37 pm »
Ok, thanks. Since I decided to wait for V17 this is currently not an option. I'll try later then...

q.