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

Functionality broken in Sublime Text 4 #49

Open
KM4YRI opened this issue Jun 17, 2021 · 9 comments
Open

Functionality broken in Sublime Text 4 #49

KM4YRI opened this issue Jun 17, 2021 · 9 comments

Comments

@KM4YRI
Copy link
Contributor

KM4YRI commented Jun 17, 2021

Functionality is broken in Sublime Text 4. They changed some APIs, and it uses Python 3.9 now, although I'm unsure of the exact details.

Is this project still being maintained? Any chance of getting an updated version that works with ST4?

@internet
Copy link

As a workaround, if you unzip the sublime-package (you can find the path in the console window when it errors), you can change the version in the .python-version file from 3.4.3 to 3.8 (or 3.3) and it appears to work correctly. There's PR already open.

@ThomasHineXYZ
Copy link

I'm also still having this issue.

This was also mentioned in issue #47, but the creator of that thread closed it...

@ThomasHineXYZ
Copy link

Looks like merge #48 fixes the issue. The owners of the repo just need to test it and merge it.

@thep0y
Copy link

thep0y commented Jun 23, 2021

Sublime Text has two built-in python interpreter versions, namely 3.3 and 3.x, of which 3.3 will not change, and 3.x will change with version updates.
The ST plug-in uses version 3.3 by default when it does not specify an interpreter.
But sublime_docblockr_python uses .python_version to specify an interpreter version 3.4.3 that has been used and is now invalid, causing the plug-in to not work properly.
Now this repository is no longer updated. It is not recommended to use this .python-version file anymore, just delete it and it will be normal.

@davi5e
Copy link

davi5e commented Jul 8, 2021

Now this repository is no longer updated. It is not recommended to use this .python-version file anymore, just delete it and it will be normal.

How to do that if there is only the DocBlockr_Python.sublime-package file in ST4 config folder?

@thep0y
Copy link

thep0y commented Jul 8, 2021

How to do that if there is only the DocBlockr_Python.sublime-package file in ST4 config folder?

DocBlockr_Python.sublime-package is essentially a compressed file, you can rename it to DocBlockr_Python.zip, then unzip it, and delete the .python-version file.
Then you should recompress it to a zip file, and rename it to DocBlockr_Python.sublime-package.
Finally, copy or move the new DocBlockr_Python.sublime-package to the Installed Packages directory.

@ThomasHineXYZ
Copy link

I ended up personally just switching to this, and it's been quite a nice replacement for this old package

https://packagecontrol.io/packages/AutoDocstring

@Freakwill
Copy link

How to do that if there is only the DocBlockr_Python.sublime-package file in ST4 config folder?

DocBlockr_Python.sublime-package is essentially a compressed file, you can rename it to DocBlockr_Python.zip, then unzip it, and delete the .python-version file. Then you should recompress it to a zip file, and rename it to DocBlockr_Python.sublime-package. Finally, copy or move the new DocBlockr_Python.sublime-package to the Installed Packages directory.

I tried it, but failed.

@thep0y
Copy link

thep0y commented Aug 25, 2022

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

No branches or pull requests

6 participants