Leap 15 - no python-MySQL-python

English Applications
1

It looks like python-MySQL-python exists for 42.3, but not for 15. Is this expected or intentional?

2

Unknown,
But you should submit a request to have it built for LEAP 15 at https://bugzilla.opensuse.org

TSU

3

I see this ticket: https://bugzilla.opensuse.org/show_bug.cgi?id=1074660
This seems to be the right ticket. But, the ‘Beta’ (and SLES) designation suggest this may not apply.
It also looks to have been in stasis for a while, is this normal?

4

The Beta designation is SLES 15 (which has had a delayed launch).
Apparently the most recent entry is that the bug has been re-assigned to the original assignee, and before the re-assignment it looks like there is a suggestion/proposal to switch from a likely deprecated codebase to one that appears to be maintained.

So,
Although this might not be at the top of a ToDo at the moment, the bug is very much active and in line to be addressed.
Since the bug lists the Assignee and QA person, you can PM either or both to get an update.

TSU

5

You do not mention what it is that requires python-MySQL-python. Could it be that the required functionality is now provided by e.g. python2-PyMySQL or python3-PyMySQL? Perhaps the calling software can be updated and/or repackaged?

6

Unfortunately no. My particular requirement is ansible. I’ve filed a bug request for support of alternate MySQL-python packages on their github support system, and the answer they come back with, most other distro’s support the fork of the original package that is maintained (won’t fix). Ansible is mentioned in the ticket I referenced in this thread, and the ticket is about the replacement, but unfortunately the package looks to be dropped and no support for the forked version.

7

MySQL-Python hasn’t received any fixes or updates in 4 years and doesn’t support Python 3.0 - that would most likely be the reason why it was dropped.

That being said, it may still compile vs 15.0 with some patches, perhaps also need specific MySQL libraries/devel packages. Honestly, I don’t see it being worth the effort.

8

I get it…

I’ll summarize again.

I’m using ansible. I know the suse community has solidified support around salt, which is clearly an excellent choice, but for my uses ansible is better (among other thing, I have a lot of aging legacy to support).

Suse support in ansible is second tier. Ubuntu and Redhat (obviously) get the best support.

I get that the original python-mysql library is dead. I’ve no issue with Leap 15 dropping support.
But…
Most distros (read Ubuntu/Redhat) seemed to have migrated to a fork:
https://pypi.org/project/mysqlclient/
Both the ansible user community and the ansible tech staff indicate that they consider this a suse issue.
But the suse team see’s this as (more or less) an ansible issue.

I can see both side of this, but I’m left out in the cold.

There was an open Bugzilla ticket about this. Ansible was explicitly mentioned, and the drop in replacement proposed.
I’d be happy if the drop in package was offered on an alternate (semi official) repository.
The ticket was closed, with no real response to the alternate package.

I could easily compile the alternate library.
But, this is a poor approach for a config management, requiring a lot of more fragile dependencies, all to allow a DSL for config management to do more or less one time Db management work.

9

Most distros (read Ubuntu/Redhat) seemed to have migrated to a fork:
mysqlclient · PyPI

Maybe you can rebuild this one:

EDIT:
Or this one without rebuild: