Open seahawks8 opened 2 years ago
👍🏻
+1
Hello @manivinesh @sfdrogojan @rhrituc
Can you please review and release this change so that it can unblock the dependencies?
Thanks, Amol
it'd be awesome if this could be merged
@BrunoJolivi can you merge?
Hi @BrunoJolivi, polite bump. I'd love to see this merged.
^^bump^^
Linking Issue 135 if this helps get it attention. @smashew any update on this would be much appreciated.
^^bump^^
+1 it would be great to get this merged
+1
if this gets merged, an angel will get its wings
@svc-scm I see that you were able to merge a PR in October, It would be great if you would be able to merge this PR.
what do you think, if this does not get merged, should I fork and push my own to maintain?
@pceric or @BrunoJolivi can you give us an update on this? We'd love to see this merged 🥺 🙏
I'm gonna lose my job if this doesn't get merged soon. Please help!
@brno32 you can fork this repository and merge it and give it a new version number, and then build your service off of your own forked version of the library. I would also suggest to everyone following this thread to please contact your SFMC sales rep and ask them to escalate this issue to someone who may have the authority to merge this PR.
@mcohoon yeah we've got our own fork as a work-around for now. Thanks for the suggestion! I've followed up with some colleagues on my end to get this escalated.
If you don't want to fork you can simply
pip install -r requirements.txt --no-deps
with these requirements:
PyJWT>=1.5.3
requests>=2.18.4
suds-community>=0.7
Salesforce-FuelSDK==1.3.0
looks like someone (me) forked this project, fixed it, and published a new version. https://pypi.org/project/Salesforce-FuelSDK-Sans/
pip install Salesforce-FuelSDK-Sans
Hello, Could someone please merge this pull request?
Heroku will be discontinuing support for its 18 stacks starting from May 1st, and it is required for the apps to migrate to the latest stack 22. However, the latest stack uses the latest version of setuptools (67~), and due to this, the SDK is not compatible with stack 22.
It is important that we address this issue as soon as possible. thanks!