chore: updating supported python versions

[Artui]

Addresses #28 issue

[kvz]

Sadly the build failed. I’m not deep into python and could signal a maintainer but perhaps you can see what’s the trouble?

perhaps the version was limited for a good reason 🤔

[Artui]

Sadly the build failed. I’m not deep into python and could signal a maintainer but perhaps you can see what’s the trouble?

perhaps the version was limited for a good reason 🤔

One of the dependencies with the current version works for python 3.7, but doesn't work for 3.12. If I update it to the version that supports 3.12, we lose support for 3.7 :D
I wonder if we're okay with losing support for 3.7?

[Acconut]

We're fine with dropping support for older Python release, but that has to part of a major release as it's a breaking change. I don't see any reason against a major release, but we might want to use this opportunity to also drop 3.8, whose support ends in November 2024: https://devguide.python.org/versions/

[Artui]

We're fine with dropping support for older Python release, but that has to part of a major release as it's a breaking change. I don't see any reason against a major release, but we might want to use this opportunity to also drop 3.8, whose support ends in November 2024: https://devguide.python.org/versions/

I'm down for that! Added this to the PR :)

[Artui]

Also updated version to 0.3.0, not sure if we want to do 1.x.x, since the version was 0.2.2 before my PR

[kvz]

When cutting major releases, I think we have to involve the experts, @arnaudlimbourg & @ifedapoolarewaj.

do we see other opportunities for upgrades that are breaking, that we should be making in this release?

[Acconut]

You misspelled @ifedapoolarewaju :)

[Acconut]

Also updated version to 0.3.0, not sure if we want to do 1.x.x, since the version was 0.2.2 before my PR

If we do a major release, it will be 1.0.0

[Artui]

Also updated version to 0.3.0, not sure if we want to do 1.x.x, since the version was 0.2.2 before my PR

If we do a major release, it will be 1.0.0

Sure, it's just been in 0.x.x for a while, just wanted to check in if it's ready for 1.0.0

[Artui]

Any updates on the status here? @kvz @arnaudlimbourg @ifedapoolarewaju

[ifedapoolarewaju]

Hi, I just realised that we need to update the version variable as well. Otherwise the SDK will be sending the wrong version to Transloadit servers.

When we do that, we'd need to update this line in the test so it passes

[Artui]

Hi, I just realised that we need to update the version variable as well. Otherwise the SDK will be sending the wrong version to Transloadit servers.

When we do that, we'd need to update this line in the test so it passes

Thanks! Updated

[Artui]

Pinging once more, just to check in :)
@ifedapoolarewaju @arnaudlimbourg

[Artui]

I see that all the tests have passed now, thanks for approving the pipeline. How long would it take to get a release out there? I don't see a PyPi deployment piece in the Github Actions code, so I assume it's a manual process done by one of the maintainers?

[ifedapoolarewaju]

This looks all good to me.
@kvz @Acconut would there be any other objections to merging this?

[Acconut]

Looks good, thanks for the feedback!

[Artui]

Awesome, thanks!

[Acconut]

One more thing: Can you please update the README? It currently says:

Only Python 3.7+ versions are supported.

[Artui]

@Acconut I've updated that and updated CHANGELOG as well.
Can you merge it and push the new version to PyPi?

[Acconut]

@cdr-chakotay Could you merge and release this PR?

[cdr-chakotay]

@cdr-chakotay Could you merge and release this PR?

Sure, we have had some internal discussions on further release.
I am not 100% convinced with the major version.
Will come back to you :)

[cdr-chakotay]

@Artui Merged this one and will release soon. Thanks for your contribution!