Handled exceptions reported as unhandled on Python 3.x



My configuration is VS 2012 Ultimate on Windows 8 Pro x64 with PTVS 2.0RC, Python 3.3.2 32-bit and Django 1.5.4. I've added virtualenv with Python and installed Django using pip, so I don't think that there is anything I missed here.

Thrown exception is :
builtins.IndexError occurred
Message: list index out of range
It occurs in C:\Python33\Lib\sre_parse.ph on line 135:
  1. def __getitem__(self, index):
  2. if isinstance(index, slice):
  3. return SubPattern(self.pattern, self.data[index])
  4. return self.data[index]
I have no idea where the problem is. I've reinstalled PTVS and Python twice, but it solved nothing.
It worked without any issues with Python 2.7 virtualenv, but I need to work with 3.3.2.


ingdavidlopez wrote Apr 14, 2014 at 5:37 PM

I downloaded the 2.1 beta version (April 7 2014) and the problem persists. I use VS 2013 Shell integrated.
I this intended?
This is my full configuration:

Microsoft Visual Studio 2013 Shell (Integrated)
Version 12.0.30110.0 REL
Microsoft .NET Framework
Version 4.5.50938

Installed Version: IDE Standard

Team Explorer for Visual Studio 2013 06154-004-0430007-02376
Microsoft Team Explorer for Visual Studio 2013

Visual C# 2013 06154-004-0430007-02376
Microsoft Visual C# 2013

Python Tools for Visual Studio 2.1.20319.03
Python Tools for Visual Studio provides IntelliSense, projects, templates, Interactive windows, and other support for Python developers.

Python Tools for Visual Studio - Django Integration 2.1.20319.03
Provides templates and integration for the Django web framework.

Python Tools for Visual Studio - Profiling Support 2.1.20319.03
Profiling support for Python projects.

SQL Server Data Tools 12.0.30919.1
Microsoft SQL Server Data Tools

pminaev wrote Apr 22, 2014 at 9:08 AM

Hi David, can you please describe your case in more detail? i.e. which version of Python you're using, and what exceptions do you see being reported that you don't expect to be?

Also, can you please check Debug -> Exceptions to make sure that your current exception reporting settings are not the cause of this?