Opened 3 years ago

Closed 3 years ago

#62265 closed defect (invalid)

py-astunparse: @1.6.3: test failures for new Python 3.9 subport

Reported by: mascguy (Christopher Nielsen) Owned by: cjones051073 (Chris Jones)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: py-astunparse

Description (last modified by mascguy (Christopher Nielsen))

While new subport py39-astunparse builds successfully, numerous tests fail.

Of note, tests succeed for subports < 3.9, suggesting that 3.9 compatibility isn't quite there yet. That was also supported by my research into Python 3.9 compatibility for ports such as py-astunparse, among other key dependencies for py-tensorflow, two weeks ago.

If the Python 3.9 subport is intended to be a placeholder, with the caveat that it may not be fully functional yet, that's fine. (With the caveat that a port note, succinctly stating that, probably should be added.)

However, if the hope was to provide a 100% functional subport - particularly to support tensorflow - that may not be possible quite yet. (Important note: Our port for py-astunparse is already using the latest released version - 1.6.3 - so we can't upgrade it at the present time.)

Logs attached for two test runs:

  • Tests for py38-astunparse, which succeed.
  • Tests for py39-astunparse, which fail.

Attachments (2)

py38-astunparse-1.6.3-test-success.txt.gz (5.4 KB) - added by mascguy (Christopher Nielsen) 3 years ago.
py39-astunparse-1.6.3-test-failures.txt.gz (8.9 KB) - added by mascguy (Christopher Nielsen) 3 years ago.

Download all attachments as: .zip

Change History (5)

Changed 3 years ago by mascguy (Christopher Nielsen)

Changed 3 years ago by mascguy (Christopher Nielsen)

comment:1 Changed 3 years ago by mascguy (Christopher Nielsen)

Description: modified (diff)

comment:2 Changed 3 years ago by mascguy (Christopher Nielsen)

Of note, py-astunparse still isn't officially supported for Python 3.9. And sadly, the latest version (v1.6.3) was released on 12/2019, with no updates since.

Hopefully that will change soon, but still TBD.

comment:3 Changed 3 years ago by mascguy (Christopher Nielsen)

Resolution: invalid
Status: assignedclosed

Since this is purely an upstream issue - and there's nothing we can do to fix it - there's not much point to keeping this open.

Note: See TracTickets for help on using tickets.