#66803 closed defect (fixed)

py310-contourpy @1.0.7: TypeError: expected string or bytes-like object

Reported by: sgrewe (Stefan Grewe) Owned by: reneeotten (Renee Otten)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc: sgrewe (Stefan Grewe)
Port: py-contourpy

Description

py310-contourpy fails to build (while py311-contourpy does build successfully)

Attachments (4)

main.log (71.6 KB) - added by sgrewe (Stefan Grewe) 22 months ago.
main.2.log (73.4 KB) - added by sgrewe (Stefan Grewe) 22 months ago.
main.log for py310-contourpy with -t
main.3.log (75.7 KB) - added by sgrewe (Stefan Grewe) 22 months ago.
main.log for py311-contourpy with -t
main.4.log (70.5 KB) - added by sgrewe (Stefan Grewe) 21 months ago.
sudo port clean --all py310-contourpy && sudo port -dvs install py310-contourpy

Download all attachments as: .zip

Change History (14)

Changed 22 months ago by sgrewe (Stefan Grewe)

Attachment: main.log added

comment:1 Changed 22 months ago by ryandesign (Ryan Carsten Schmidt)

Owner: set to reneeotten
Port: py-contourpy added; py310-contourpy removed
Status: newassigned
Summary: py310-contourpy fails to buildpy310-contourpy @1.0.7: TypeError: expected string or bytes-like object

comment:2 Changed 22 months ago by reneeotten (Renee Otten)

it did build fine on my system when I did the update and also the buildbots succeeded in building the py310 ports for pretty much every system.... so I am not really sure why it doesn't work for you.

Is this by chance an issue that only shows up on "arm64" architecture; can you compare the main.log files (or upload here) for the py310 and py311 installs and see if there is anything that seems off there?

Changed 22 months ago by sgrewe (Stefan Grewe)

Attachment: main.2.log added

main.log for py310-contourpy with -t

Changed 22 months ago by sgrewe (Stefan Grewe)

Attachment: main.3.log added

main.log for py311-contourpy with -t

comment:3 Changed 22 months ago by sgrewe (Stefan Grewe)

After deleting and trying to resinstall py311-contourpy to get to the log, this is now also failing. Attaching main.log for both in trace mode

comment:4 in reply to:  3 Changed 21 months ago by reneeotten (Renee Otten)

Replying to sgrewe:

After deleting and trying to resinstall py311-contourpy to get to the log, this is now also failing. Attaching main.log for both in trace mode

building in trace-mode doesn't work currently on Ventura - that's a known issue (see 66803) so these log files are not very helpful as they don't show the actual build problem. The log file you want to attach is the one that is generated when doing the following: sudo port clean --all py311-contourpy && sudo port -dvs install py311-contourpy.

I just tried it myself locally and it works fine with the caveat that I don't have an arm64 machine so if the issues is related to that I have no way of troubleshooting it. If someone else with an arm64 machine can give it a try that would be much appreciated.

Changed 21 months ago by sgrewe (Stefan Grewe)

Attachment: main.4.log added

sudo port clean --all py310-contourpy && sudo port -dvs install py310-contourpy

comment:5 Changed 21 months ago by sgrewe (Stefan Grewe)

Strangely, sudo port clean --all py311-contourpy && sudo port -dvs install py311-contourpy is now working again, but sudo port clean --all py311-contourpy && sudo port -dvs install py311-contourpy is not working. main.log attached

comment:6 Changed 21 months ago by sgrewe (Stefan Grewe)

Sorry for the misprint above, I meant sudo port clean --all py310-contourpy && sudo port -dvs install py310-contourpy is not working

comment:7 Changed 13 months ago by reneeotten (Renee Otten)

Cc: sgrewe added

has duplicate 68327

comment:8 Changed 13 months ago by reneeotten (Renee Otten)

as I said before, I cannot reproduce the problem (it works fine on macOS Sonoma, XCode 15, x86_64) so not sure what to do about it.

I would do an update to the latest upstream version (currently 1.1.1) but that is complicated by the fact that upstream switched to meson-python as build backend and that requires quite some additional work (cf. 68208) for which I don't have time right now.

comment:9 Changed 12 months ago by reneeotten (Renee Otten)

I updated the port to version 1.1.0 recently - can you please check whether this issue still persists?

comment:10 Changed 12 months ago by reneeotten (Renee Otten)

Resolution: fixed
Status: assignedclosed

okay, I am assuming that the update fixed this issue. If not feel free to re-open.

Note: See TracTickets for help on using tickets.