Thanks for the pull request! Could you please rebase it on the current master branch, so that workflows run correctly? Also I noticed that you have provided an implementation of Dijkstra algorithm using set, which unfortunately wouldn't work because Python's sets are based on hash-tables, and as such don't produce the smallest element.

What you actually want here is probably heapq, could you please update the pull request using it? Also, did you check your code on any specific problems?

Thanks for the pull request! Could you please rebase it on the current master branch, so that workflows run correctly? Also I noticed that you have provided an implementation of Dijkstra algorithm using set, which unfortunately wouldn't work because Python's sets are based on hash-tables, and as such don't product the smallest element.

What you actually want here is probably heapq, could you please update the pull request using it? Also, did you check your code on any specific problems?

Sure, tried to follow the C++ original as much as possible. It worked for several test cases, but I'll switch to heapq and rebase.

@clumsy Please don't indent codeblock's backticks in markdown i.e. make sure ```cpp stays at the beginning on the line.

Indenting here is okay, because it uses Material's content tabs feature.

Indenting here is okay, because it uses Material's content tabs feature.

Exactly, without this change there are no C++/Python tabs to switch from. This follows the same format as other pages with examples in two languages.

Personally I think there should only be one implementation, and a good reason to have multiple. If we have python as pseudocode, then it shouldn't be hidden in a content tab. My 2c

I'm generally fine with having both C++ and Python. The latter is more beginner-friendly, mostly simple to review and can also be used in problems where performance doesn't matter as much, e.g. for Project Euler problems, which is also the reason I've included both in continued fractions article (well, and also because with continued fractions, you are much more likely to require big integers). I think it's fine to use it as a second default, when available. It doesn't really take anything from article's quality, and can be useful for some people.

Hiding it in content tabs is, IMO, fine because the majority of CPers still use C++, and using tabs allows to preserve article space, so that only people for whom Python code would actually be useful will actually open it.

+1 to what @adamant-pwn said.
Also, I've addressed your comment, please let me know if there's more to edit.

Preview the changes for PR #1336 at https://gh.cp-algorithms.com/1336/ (current version: 9260362).

The base branch changed, will cut another PR.