Skip to content
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.

Remove suds-jurko #138

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

seahawks8
Copy link

  • Removed dependency on suds-jurko due to setuptools>=58.0.0 not supporting 2to3, pointed to suds-community
  • Removed wsgiref because it is part of the standard lib
  • Removed distribute as it is part of setuptools.

@amoldabade7
Copy link

👍🏻

1 similar comment
@bobglobe
Copy link

bobglobe commented Dec 3, 2021

+1

@amoldabade7
Copy link

Hello @manivinesh @sfdrogojan @rhrituc

Can you please review and release this change so that it can unblock the dependencies?

Thanks,
Amol

@brno32
Copy link

brno32 commented Dec 21, 2021

it'd be awesome if this could be merged

@seahawks8
Copy link
Author

@BrunoJolivi can you merge?

@mcohoon
Copy link

mcohoon commented Feb 1, 2022

Hi @BrunoJolivi, polite bump. I'd love to see this merged.

@seahawks8
Copy link
Author

^^bump^^

@seahawks8 seahawks8 closed this Feb 3, 2022
@seahawks8 seahawks8 reopened this Feb 3, 2022
@mcohoon
Copy link

mcohoon commented Feb 3, 2022

Linking Issue 135 if this helps get it attention. @smashew any update on this would be much appreciated.

@seahawks8
Copy link
Author

^^bump^^

@bogdanp05
Copy link

+1 it would be great to get this merged

@dillonkelley
Copy link

+1

@brno32
Copy link

brno32 commented Apr 7, 2022

if this gets merged, an angel will get its wings

@mcohoon
Copy link

mcohoon commented Apr 7, 2022

@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.

@seahawks8
Copy link
Author

what do you think, if this does not get merged, should I fork and push my own to maintain?

@pietercusters
Copy link

@pceric or @BrunoJolivi can you give us an update on this? We'd love to see this merged 🥺 🙏

@brno32
Copy link

brno32 commented Apr 28, 2022

I'm gonna lose my job if this doesn't get merged soon. Please help!

@mcohoon
Copy link

mcohoon commented Apr 28, 2022

@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.

@brno32
Copy link

brno32 commented Apr 28, 2022

@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.

@pietercusters
Copy link

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

@seahawks8
Copy link
Author

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

@subodhjena
Copy link

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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.