Skip to content

Conversation

tomuben
Copy link
Collaborator

@tomuben tomuben commented Apr 28, 2025

fixes #1122
fixes #1121
fixes #1124

All Submissions:

  • Check if your pull request goes to the correct bash branch (develop or master)?
  • Is the title of the Pull Request correct?
  • Is the title of the corresponding issue correct?
  • Have you updated the changelog?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Are you mentioning the issue which this PullRequest fixes ("Fixes...")

When integrating to Develop branch:

  1. Remember to merge with "Squash and Merge"

When integrating to Main branch:

  1. Remember to merge with "Merge"
  2. Have you thought about version number? If there is a breaking change in the toolchain, need to update major version.
  3. If you plan a release, have you checked the Exasol packages for updates?
    1. Websocket API (https://github.com/EXASOL/websocket-api)
    2. Exasol-BucketFS

@tomuben tomuben changed the title - #1121: Fixed time zones in Python3 only SLCs #1121: Fixed time zones in Python3 only SLCs Apr 29, 2025
@tomuben tomuben merged commit adde020 into develop Apr 29, 2025
11 of 12 checks passed
@tomuben tomuben deleted the bug/fix_timezones_in_python_slcs branch April 29, 2025 12:09
tomuben added a commit that referenced this pull request Apr 29, 2025
Changelist:
- #1121/#1122/#1124: Fixed time zones in Python3 only SLCs (#1123)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants