<p>Hi, I'm new to GO and I'm using Pycharm as my IDE. Does anybody can give an update regarding GO debugging? I understand that print/log is (was) the way but can we see some progress toward decent debugging tool?</p>
<hr/>**评论：**<br/><br/>PaluMacil: <pre><p>I don't use PyCharm for Go. In VS Code I debug with Delve via the plugin available in extensions, giving me step debugging, step in / out, variable lists, and watches. Since Delve is a free-to-use project, I expect it's the choice for Gogland. Since Gogland is in preview stages, I don't think the plugin will get much development work until the new IDE is released. Two of the contributors to the plugin were JetBrains employees, I believe, so I wouldn't be surprised if they return to improve the plugin after further work on Gogland.</p>
<p>If you are fine with VS Code, I do recommend it with Go, and that's coming from being a PyCharm Pro user as well.</p></pre>_nefario_: <pre><p>the old plugin for PyCharm and IntelliJ doesn't really work well anymore. the debugger was always really slow and never worked for tests. </p>
<p>for now, i'd recommend trying out JetBrains' Gogland IDE. the debugger there does more what you'd expect. its not exactly perfect, especially when stepping into go's standard library code, but overall, its pretty good.</p></pre>dlsniper: <pre><p>Delve is doing a lot of the good work for debugging but there's a problem with Go itself not producing the right or at all information needed in order to debug applications sometimes, which can make the experience less than ideal. As such, always try and use the latest version and Go, as there are usually a lot of changes between Go 1.7 and Go 1.8 for example, and the latest for delve.</p>
<p>Just make sure that you are using the JetBrains maintained Go plugin, not the older community one, and you'll benefit from the latest developments there, including having a more update version of delve. </p></pre>
