it happens when dealing with multiple threads
@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 BinanceSocketManager it works fine. I've updated the intelligence db but it still says the same
as you can see in the latest screenshot I can import it fine from the interactive shell
I tried restarting VS but same thing.
Thank you
Thank you
@illera88 it looks like there are issues with the binance packages that were uploaded to PyPI. See https://pypi.python.org/pypi/binance/0.1 and https://pypi.python.org/pypi/binance/0.2 -- there's only one wheel file for 0.2, and it's Python 2.x only. So installing under Python 3.x will get you v0.1 installed from source, and the resulting install doesn't have the expected binance.py anywhere. You probably should contact the author to let them know about this.
It looks as in the current VS2017 it looks as if there is no f-string support. This is quite annoying in every day use because it breaks most of the code introspection features like "show references" and "refactor". I browsed the Github repository but was neither able to find the behaviour documented nor a bug ticket or a roadmap entry. Is it already fixed but just not deployed to the production version of VS2017?
@kunom There's no specific support in there yet to enable parts of the contents of
{} to be treated as code, and we haven't seen enough demand to prioritise the work (of significantly modifying our Python parser) over other items. We'll take your comment as a vote in favour. Thanks!
@zooba I understand that handling the contents of
{} means a lot of parser work. It might be an acceptable intermediate solution to extend the parser that it just accepts the prefix f for strings (like f'' and f""), so that the parsing after the f-string is less impacted than now an that the "invalid syntax" red lines go away.
Hello! I'm very new to using Visual Studio, and would like to get CookieCutter Explorer installed on Visual Studio 2015 Professional. I've installed Python tools for Visual Studio 2.2.6, and I have both python 2.7 and 3.5(64-bit) installed, via CPython and Anaconda respectively, and those both show up in the Python Environments tab in Visual Studio, with 3.5 set as the default. Afaik, the CookieCutter Explorer should be present under View > CookieCutter Explorer. Am I missing something?
Hello, Due to environment restriction my team is forced to develop and test on python 2.5. In Visual Studio 2017 I am getting an error while trying to run my unit tests saying 2.5 version of python is not supported anymore. Is there any way that we can do that in Visual Studio 2017?
@skucher Thanks for reaching out! We see so little usage of 2.5 that when we adopted JSON we chose to simply drop 2.5 support rather than provide workarounds. However, in most cases these steps should work:
- add your 2.5 environment as a custom environment and mark its version as 2.6
- install the
simplejsonpackage from PyPI - add a
sitecustomize.pyfile to your Python 2.5 install that contains:
Most of the problems that may occur with Python 2.5 are fixable in the .py files in our code, so feel free to modify those. We're open to merging pull requests to maintain Python 2.5 support (provided it doesn't impact later versions), but at this point we are no longer testing against Python 2.5 or 3.0.import simplejson, sys sys.modules['json'] = simplejson
I tried to run conda update --prefix "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Anaconda3_64" anaconda
but I got an error conda.CondaMultiError: post-link script failed for package defaults::ipykernel-4.8.0-py36_0
@davidshen84 You can if you want (make sure you run it from an administrative command prompt), it's just a regular Anaconda install. We periodically update the version included with the Visual Studio installer, and so updating Visual Studio will update the version of Anaconda at the same time.
For that error message, is there are more information in the output? I can take a look and see if there's something obviously wrong, but I suspect you'll be best to report it to Anaconda's support channels. You can also uninstall Anaconda through Visual Studio and install it manually from https://anaconda.com if you want a "regular" install - we will still detect it in Visual Studio just fine.
Also, forgot to say I'm using qt5, PyQt5
hey there!
I've been using PTVS for a long time but I've never faced the problem I just did:
I have a fresh windows installation and installed visual studio with python support. I can create python projects but for some reason when I click on
I've been using PTVS for a long time but I've never faced the problem I just did:
I have a fresh windows installation and installed visual studio with python support. I can create python projects but for some reason when I click on
start it just does nothing. I'm just using a simple hello world and trying to hit a breakpoint in the print instruction but nothing happens
I can't see anything in the output tab. I thought it was related with the python environments but i've tried multiple and that seems not to be the problem.
Using Windows 10 x64 Visual Studio 2017 Professional
Using Windows 10 x64 Visual Studio 2017 Professional
found out that when I
start without debugging it actually runs the code. It just seems that nothing is run if I just press F5 or click on Start
I get this with the experimental one:
warning: Debugger speedups using cython not found. Run '"C:\Python27.15-x64\python.exe" "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd\pydevd\setup_cython.py" build_ext --inplace' to build.
and this when actually running what it ask for:
C:\windows\system32>"C:\Python37-x64\python.exe" "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd\pydevd\setup_cython.py" build_ext --inplace
running build_ext
building '_pydevd_bundle.pydevd_cython' extension
creating build
creating build\temp.win-amd64-3.7
creating build\temp.win-amd64-3.7\Release
creating build\temp.win-amd64-3.7\Release\_pydevd_bundle
C:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\VC\Tools\MSVC\14.14.26428\bin\HostX86\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Python37-x64\include -IC:\Python37-x64\include "-IC:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\VC\Tools\MSVC\14.14.26428\ATLMFC\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\Preview\Professional\VC\Tools\MSVC\14.14.26428\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17134.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17134.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17134.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17134.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17134.0\cppwinrt" /Tc_pydevd_bundle/pydevd_cython.c /Fobuild\temp.win-amd64-3.7\Release\_pydevd_bundle/pydevd_cython.obj
pydevd_cython.c
_pydevd_bundle/pydevd_cython.c(28837): error C2039: 'exc_type': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28838): error C2039: 'exc_value': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28839): error C2039: 'exc_traceback': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28846): error C2039: 'exc_type': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28847): error C2039: 'exc_value': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28848): error C2039: 'exc_traceback': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28849): error C2039: 'exc_type': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28850): error C2039: 'exc_value': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28851): error C2039: 'exc_traceback': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28896): error C2039: 'exc_type': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28897): error C2039: 'exc_value': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28898): error C2039: 'exc_traceback': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28899): error C2039: 'exc_type': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28900): error C2039: 'exc_value': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(28901): error C2039: 'exc_traceback': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(29032): error C2039: 'exc_type': is not a member of '_ts'
c:\python37-x64\include\pystate.h(209): note: see declaration of '_ts'
_pydevd_bundle/pydevd_cython.c(29033): error C2039: 'exc_value': is not a member of '_ts'
c:\python37-x64\include\pystate.
@illera88 Currently only Python 3.6 IIRC, though I'm petitioning the
ptvsd team to expand that. Feel free to post issues on https://github.com/Microsoft/ptvsd requesting it :)
@ThomasThelen It is not. VS for Mac is a totally different product and we would have to reimplement most of the Python support to make it work there. Currently we are focused on Visual Studio 2017 and VS Code - the latter works fine on Mac, so we suggest trying that out.
I was reading the issues about embedding Jupyter Notebooks in Visual Studio itself, although I don't understand why this will (probably?) not happen. How I would see this: when opening a .ipynb file, start a NB server at project root (with an interpreter of choice), and render the .ipynb file. What's the catch here?
I you guys would like to have that, I want to help here (will need some guidance though!)