Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It would be nice if the Python API would use the 'new style' python object #3104

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2012-06-18 16:24:59 +0200
From: @gijzelaerr
To: clients devs <>
Version: -- development

Last updated: 2012-07-18 11:15:47 +0200

Comment 17368

Date: 2012-06-18 16:24:59 +0200
From: @gijzelaerr

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0
Build Identifier:

Probably this would require a split of a Python2 and a Python3 version of the API.

Reproducible: Always

Comment 17439

Date: 2012-07-10 10:55:02 +0200
From: @gijzelaerr

Yes, this would require a split of the python code into a python2 and python3 version, which now seems to be a better solution anyway.

When I find the time i'll spilt the 2 versions (in the trunk), and do some more python version specific changes - and also update the debian packages.

Comment 17501

Date: 2012-07-18 11:04:43 +0200
From: @grobian

are commits
anywhere related to this, and/or do they fix/implement this bug?

Comment 17503

Date: 2012-07-18 11:12:35 +0200
From: @gijzelaerr

yes, was about to close this bug. The python2 api in the trunk uses 'new style' objects now.

Comment 17504

Date: 2012-07-18 11:15:47 +0200
From: @grobian

Can you make a ChangeLog entry for this? It is a feature that got implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant