This won't change anything, the PUBLIC_COMMANDS and PRIVATE_COMMANDS lists are all the possible commands that poloniex provides. marketTradeHist already has its own 'special' method to work around the duplicate names: https://github.com/s4w3d0ff/python-poloniex/blob/master/poloniex/__init__.py#L225

Changing the name in the PRIVATE_COMMANDS list will not change anything because that method doesn't use that list to determine what command to use.

The __call__ method (https://github.com/s4w3d0ff/python-poloniex/blob/master/poloniex/__init__.py#L137) uses the PUBLIC_COMMANDS and PRIVATE_COMMANDS lists to determine if the command is valid, and what api to use (public or private).

I could remove the command string from the PUBLIC_COMMANDS and 'Poloniex.marketTradeHist()' would still work.

It was more for clarifying the confusion. From my point of view, a user might be calling Poloniex. returnTradeHistory() thinking it's the public method when in reality its 'Poloniex.marketTradeHist().

I definitely think that should be clarified.

Thanks a lot for taking the time to respond 👍

Unfortunately, the only problem with this workaround is that you can't access the public trade history using Poloniex('returnTradeHistory, args) (it defaults to the private version), you have to use Poloniex.marketTradeHist().

I'll try to remember to add a wiki page and update the docstrings to try and reduce confusion.

Awesome thanks a bunch 👍