IntelliSense for .pyd requires matching Python architecture

[mloskot]

I don't think the following issue is documented anywhere, but for some it may not be obvious.

In order to make Visual Studio PyTools IntelliSense work for a .pyd extension, it is required to select, in Project > Properties > General > Interpreter, Python interpreter matching target architecture of the .pyd binary.

Especially, if is relevant if both 32-bit and 64-bit Python installations are hosted side-by-side.

For instance, given side-by-side installation of the two Python interpreters:
C:\Python32 which is 64-bit version
C:\Python32x86-32 which is 32-bit version
if a .pyd is installed in C:\Python32 only, then one may need to choose "Python 64-bit 3.2" as the project interpreter.

Otherwise,

1. IntelliSense won't be available.
2. An attempt to manually add 64-bit .pyd to References of a project that is configured to target Python 32-bit will fail as well.

[zooba]

It's not so much an issue as by-design behaviour (you can't import .pyd files with incompatible interpreters, so we don't show you the import when you've chosen an incompatible interpreter), but there's no harm in clarifying it on our wiki.

[mloskot]

On 27 Apr 2015 20:30, "Steve Dower" notifications@github.com wrote:

you can't import .pyd files with incompatible interpreters,
so we don't show you the import when you've chosen
an incompatible interpreter

Hmm what do you're mean by "we don't show you the import"?

The by design is clear, it's just it may not be as obvious as it seems.

[huguesv]

We're closing old issues with no recent activity. If this is still important, please open a new issue.

[mloskot]

That's fine