AdamYoblick on change_package_feeds
update third party notices Clean up prebuild powershell, a… move to public azure feed for n… and 5 more (compare)
ptvsdand VS are tightly linked and there were breaking changes between versions (and as you can tell, we are not and never have been using SemVer for this package)
@zooba @int19h sorry for hijacking this chat, but is there anyone in PTVS team who can review this code for properly finalizing and garbage collecting PyObject in pythonnet? I see that you use a lot of SuppressFinalize and safehandles, so you might be able to review this:
The code is really mind-boggling to me.
I cannot seem to get
ptvsd (3.0.0) working with my Flask application.
FLASK_DEBUG to false to prevent the live reload or
werkzeug debugger causing issues.
I can see in
netstat the python process waiting for the debugger to attach on port
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:5555 0.0.0.0:* LISTEN 7/python
When I attempt to connect I just get.
Debug adapter process has terminated unexpectedly
With no information in the Debug Console as to why it failed.
If I reload VSCode and attempt to attach again it appears to connect, but again no output in the Debug Console and the breakpoints are all inactive.
3.x.y"x" part of the number, but the "y" automatically updates and is enough for us to find the matching sources. Each Visual Studio version, however, has exactly one PTVS version, so if you're on the latest VS then you have the latest PTVS that is available to you.
@illera88 Sorry to have missed your messages (I was travelling at the time). If you're using VS 2017 and it isn't prompting you to update, then you're on the latest. If you are doing remote debugging, then
pip install -U ptvsd on the remote machine will make sure you have the latest debugger (which you'll need if you have the latest VS 2017).
However, if you're doing multithreaded debugging, it's equally likely that you've discovered a bug. We're doing some heavy work on our debugger right now (expect an announcement in the next week or two), so we're unlikely to consider a bugfix to the old one, but if you can report an issue with enough info for us to reproduce it we can make sure it works with the next version.
ModuleNotFoundError: No module named 'binance.websockets'; 'binance' is not a package. If I open a shell and do
from binance.websockets import BinanceSocketManagerit works fine. I've updated the intelligence db but it still says the same