[ENH] shorten package import path on v2 release?

[fkiraly]

I am wondering whether we should shorten the package import path on the v2 release, from pytorch_forecasting to ptf. Simply out of user convenience.

As a downwards compatibility measure, we can forward pytorch_forecasting imports to ptf.

Thoughts?

[phoeenniixx]

Hmm, I think this is a nice idea!
I think we should add this to our work items - to be added from next beta release
For v2, we could also completely drop ptf? as we would be anyway adding many breaking changes, so some small path change would not be that much of an effort comparatively I assume.
What do you think?

[fkiraly]

For v2, we could also completely drop ptf?

Do you mean, pytorch_forecasting?

I would not advise this, because there are books and tutorials that will have the old statement. Books in particular are impossible to update, so I think it should continue working indefinitely while raising a warning.