search

shepilov-vladislav / wdb_server_aiohttp

Drop-in replacement for https://github.com/Kozea/wdb/tree/master/server, but rewritten with aiohttp
GNU General Public License v3.0
24 stars 2 forks source link

state of this project #696

Open fessacchiotto opened 1 year ago

fessacchiotto commented 1 year ago

hello! thanks for your work on this porting of wdb. is this project still maintained?

shepilov-vladislav commented 1 year ago

It all depends on how many people use it. I think it may already have faded into oblivion. I don't know of any scenarios where it can't be replaced by other debuggers

arkhan commented 1 year ago

It all depends on how many people use it. I think it may already have faded into oblivion. I don't know of any scenarios where it can't be replaced by other debuggers

What alternatives exist that offer a similar experience to this project?

fessacchiotto commented 1 year ago

For example, I have really enjoyed wdb using vim as editor and put a trace statement in the code at any point to raise the debugger. It has been a great tool (and it could still be…). Now I’m still using vim for most of editing and just when I need to debug the python code I’m using vscode (as a debugger only, practically). On 6 Jul 2023, at 18:21, arkhan @.***> wrote:

It all depends on how many people use it. I think it may already have faded into oblivion. I don't know of any scenarios where it can't be replaced by other debuggers

What alternatives exist that offer a similar experience to this project?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

shepilov-vladislav commented 1 year ago

Thank you for your activity on my project @fessacchiotto and @arkhan!

I would quite sincerely like to develop this project, because at one time I made a fork because the author of the original project abandoned it and it had a lot of bugs and lacked test coverage. And at that time wdb was my main debugger and covered all my needs. Then VS Code appeared and it completely buried the project, because there are no tasks that could not be realized using VS Code Debugger. At the same time VS Code buried a lot of adequate editors - for example Sublime Text 2 (I really loved it, I liked writing my plugins in Python). Now I don't see how my wdb fork can be better than VS Code Debugger and what unique features could resurrect it. WDB still needs to update the frontend part and add a display of the list of local and global variables. But unfortunately I don't have that much javascript experience yet.