Problem with Path module

[thomashollier]

Thanks a lot for your work making this available on M1 macs. It's so much better for me to be able to run this on my local machine.

I grabbed your last "build-PIP-TAR #179" and there seems to be some kind of confusion between pathlib and os.path. When I click on the render button, nothing happens and the traceback says: AttributeError: 'Path' object has no attribute 'abspath'

I grabbed an older version and the problem wasn't there. I tried to figure out what file it was coming from but I'm not a dev and couldn't figure it out.

[jdegenstein]

First off, thanks for reporting -- I hadn't noticed this issue before and I was immediately able to reproduce the issue. According to the release notes for path==17.0.0 the abspath method was removed. I removed reference to abspath and replaced with absolute instead and it is tested and working on my machine.

https://github.com/jaraco/path/blob/757d8a3bdf7a94f95d392215b9586589b99f7a81/NEWS.rst#L7

Glad to hear the Apple silicon has worked out well for you in the past. Can you confirm the new build here is working correctly on your machine? I would like to publish a release with all 4 supported platforms/CPUs soon but have been unable to test the Apple silicon version.

new build:
https://github.com/jdegenstein/jmwright-CQ-Editor/actions/runs/10513000076

[thomashollier]

That fixed it. A couple of notes on additional steps I had to take:
Changed to cocoa:
QT_QPA_PLATFORM=cocoa

Also, Apple's security system (gatekeeper) required me to tag all the included binaries as approved, and it took me a while to figure out the efficient way to do all the .so and .dylib files in the terminal.

enable the ApprovedApps label:

sudo spctl --enable --label "ApprovedApps"

apply the label to all the executables in the directory:

for a in find CQ-editor -type f -name "*so"; do; sudo spctl --add --label "ApprovedApps" $(pwd)/$a;done
for a in find CQ-editor -type f -name "*dylib"; do; sudo spctl --add --label "ApprovedApps" $(pwd)/$a;done
sudo spctl --add --label "ApprovedApps" CQ-editor/CQ-editor

Or one could disable the security altogether but not really recommended:
sudo spctl --global-disable
sudo spctl --master-disable

[jdegenstein]

I went ahead and published a new release (including MacOS-arm64), but I have not had a chance to add the ApprovedApps labeling yet. I did add the QT_QPA_PLATFORM=cocoa that you suggested.

[thomashollier]

Great, thanks! I'm not sure how the ApprovedApp label thing work exactly but I think it's not something you can do on your end and has to be done by the user.

…

On Tue, Sep 17, 2024 at 11:29 AM jdegenstein ***@***.***> wrote: I went ahead and published a new release (including MacOS-arm64), but I have not had a chance to add the ApprovedApps labeling yet. I did add the QT_QPA_PLATFORM=cocoa that you suggested. — Reply to this email directly, view it on GitHub <#20 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADCJ3MUORVPTWYD237EGEG3ZXBYKLAVCNFSM6AAAAABM5I4IAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGYZDGNZZGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Thomas Hollier, VFX Supervisor and Digital Artist (310) 463-1327 art: https://www.relentlessplayart.com vfx: https://www.relentlessplayvfx.com -------

[jdegenstein]

Yeah I think you are right, wondering if I can include a script at least so the user can run it and help streamline the process?