How to resolve "Magic Comment" error for installing PyPI package with different import name?

would you consider this a known issue, or should we create a bug report?

(Sorry for the @ spam, not sure if you’d see the message otherwise?)

The /tmp dir has full write permissions, but if you look at the error message, it’d trying to write to /home/sbx… which doesn’t exist, hence the error

Oh, I assumed sbx_user1051 was the Pipedream user

Does the package let you specify where to place /tmp files?

Nah I’m actually not sure where that’s coming from. It might be the user the Amazon Linux runtime automatically creates

That’s what I’m looking for right now, but this seems to occur during install

# pipedream add-package pinecone-client

I don’t think the worker got to the handler function

The error shows at the top of the builder

The placement of the error is misleading, and it’s a known issue unfortunately.

The error is happening at workflow build time, when the workflow is being compiled with your PyPI dependencies.

This is another good candidate for an issue on our public GH: Sign in to GitHub · GitHub

Got it, I’ll make an issue

I’ve seen some other packages have gotten “hotfixes” basically in some of the closed issues on GitHub. Any chance that might happen with pinecone? Deciding on whether I continue down the pipedream path for my application or if I need to break out into lambda :face_vomiting:

yeah I’d love to support Pinecone, I can look into this more — just assigned myself the issue. I can’t promise an ETA but should have time to look into it next week and see what the blocker is

Sounds good. Thanks !

Posted thread to Discourse: How to resolve error while using Magic Comment for PyPI package with different import name?

Any luck on this one yet, ?

Not yet, hoping to get some time on it today or tomorrow and will update you ASAP

I’m adding my name to the list. I created a custom package and uploaded it to PyPi. Trying to use the package throws the following error related to requirements. Not sure if it’s related to this issue or if it’s something else.