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

DE-699 | Update global server logs retrieval #299

Merged
merged 3 commits into from
Nov 23, 2023
Merged

DE-699 | Update global server logs retrieval #299

merged 3 commits into from
Nov 23, 2023

Conversation

aMahanna
Copy link
Member

@aMahanna aMahanna commented Nov 22, 2023

  • announcing deprecation of arango.database.Database.read_log
  • new arango.database.Database.read_log_entries method

Comment on lines +618 to +621
"""Read the global log from server. This method is deprecated
in ArangoDB 3.8 and will be removed in a future version
of the driver. Use :func:`arango.database.Database.read_log_entries`
instead.
Copy link
Member Author

@aMahanna aMahanna Nov 22, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to adjust the way we address this for a better solution (I am following this precedent).

We could for example use the @deprecated decorator if we add the Deprecated package as a dependency.

Copy link
Member

@apetenchea apetenchea Nov 22, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think having the comment is great, but we should make it visible for users that are not going through the documentation. Or, for example, if they use another package that is built on top of python-arango, they should be able to figure out that there is a problem underneath (ok, this may be an exaggerated example, but you know what I mean).
Using the @deprecated decorator would do just fine. I'm not familiar with it, but a requirement that I find sensible is to allow to user to disable it the warning.
A slightly different approach that I used before is to emit a warning using the standard library, for example here. FutureWarning or DeprecatedWarning would be fit the bill (the latter is disabled by default).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense!

I've added a warn(..., DeprecationWarning) call in dd7383a

@aMahanna aMahanna requested a review from apetenchea November 22, 2023 13:59
Copy link
Member

@apetenchea apetenchea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change looks good. We should take a moment to decide upon emitting some kind of warning, either using a decorator as you pointed out, or standard warn.

@aMahanna aMahanna merged commit 9474172 into main Nov 23, 2023
52 checks passed
@aMahanna aMahanna deleted the DE-699 branch November 23, 2023 15:54
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