Release version update

[henrykironde]

No description provided.

[ethanwhite]

LGTM

[henrykironde]

@ethanwhite do you think we should amend/squash the second commit or leave it in the history?

[ethanwhite]

@ethanwhite do you think we should amend/squash the second commit or leave it in the history?

No strong feelings. It's a weird situation. Whatever you think is best is good by me

[ethanwhite]

When I install this PR and check for the version in Python I get an error:

import deepforest
deepforest.__version__

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[2], line 1
----> 1 deepforest.__version__

AttributeError: module 'deepforest' has no attribute '__version__'

This works as it should in 1.3.3. I'm not sure if the issue in in this PR elsewhere, but we should fix it here.

[henrykironde]

@ethanwhite with the current structure we have

>>> from deepforest._version import __version__
>>> __version__
'1.4.1'

[ethanwhite]

Is that a new Python standard?

[ethanwhite]

I'm booked most of the afternoon so @henrykironde just go with what you think is best. My thinking was based on deepforest.__version__ being a de facto standard:

https://stackoverflow.com/questions/458550/standard-way-to-embed-version-into-python-package

But if that has changed I'm fine with doing it differently. I'm going to change to Approve so that I'm not blocking you and @bw4sz finishing off the release