Thanks to both of you for the info. It'll take me a while to dig through
it and make sense of it all.
Today I was able to install visual studio community 2015 for use with
python 3.5. Then I tried using pip to install python-pptx and xlwings. I
believe on xlwings I got the following error (in part) didn't know if the
whole thing would be useful. Thinking about this I'm not sure if this a
compiler issue or a situation where lxml isn't supported in 3.5 yet.
Might someone be able to shed some insight?
Thanks,
Jeff
...
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\cl.exe /c
/nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Users\vandeje1\AppDat
a\Local\Temp\1\pip-build-ih2xe4gw\lxml\src\lxml\includes
-IC:\Users\vandeje1\AppData\Local\Programs\Python\Python35-32\include -IC:\
Users\vandeje1\AppData\Local\Programs\Python\Python35-32\include
"-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE"
"-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE"
"-IC:\Program Files (x86)\Windows Kits\10\include\10.0.101
50.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.6\include\um"
"-IC:\Program Files (x86)\Windows Kits\8.1\include\shared
" "-IC:\Program Files (x86)\Windows Kits\8.1\include\um" "-IC:\Program
Files (x86)\Windows Kits\8.1\include\winrt" /Tcsrc\lxml\lxml.
etree.c /Fobuild\temp.win32-3.5\Release\src\lxml\lxml.etree.obj -w
cl : Command line warning D9025 : overriding '/W3' with '/w'
lxml.etree.c
C:\Users\vandeje1\AppData\Local\Temp\1\pip-build-ih2xe4gw\lxml\src\lxml\includes\etree_defs.h(14):
fatal error C1083: Cannot ope
n include file: 'libxml/xmlversion.h': No such file or directory
C:\Users\vandeje1\AppData\Local\Programs\Python\Python35-32\lib\distutils\dist.py:261:
UserWarning: Unknown distribution option:
'bugtrack_url'
warnings.warn(msg)
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio
14.0\\VC\\BIN\\cl.exe' failed with exit status 2
----------------------------------------
Command
"C:\Users\vandeje1\AppData\Local\Programs\Python\Python35-32\python.exe -c
"import setuptools, tokenize;__file__='C:\\Users\
\vandeje1\\AppData\\Local\\Temp\\1\\pip-build-ih2xe4gw\\lxml\\setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read(
).replace('\r\n', '\n'), __file__, 'exec'))" install --record
C:\Users\vandeje1\AppData\Local\Temp\1\pip-yz3bhof7-record\install-rec
ord.txt --single-version-externally-managed --compile" failed with error
code 1 in C:\Users\vandeje1\AppData\Local\Temp\1\pip-build-
ih2xe4gw\lxml
On Sun, Sep 27, 2015 at 2:10 PM, eryksun <eryk...@gmail.com> wrote:
> On Sat, Sep 26, 2015 at 4:40 PM, Jeff VanderDoes
> <jeffvanderd...@gmail.com> wrote:
> >
> > I'm fairly new to Python and was excited to start playing with it until I
> > ran into need to compile some extensions under windows 7 64 bit. I've
> done
> > some searching but after more hours than I care to count being
> unsuccessful
> > setting up MS visual studio (2015, 2012, and 2010) with service packs and
> > SDKs I can tell I'm spinning my wheels and going nowhere fast.
>
> For 3.5 you should be able to just install Visual Studio 2015
> Community Edition. This is the current release of Visual Studio, so if
> you encounter problems, at least finding help won't be one of them.
>
> 2.7 is built with VS 2008, which is no longer supported. But, thanks
> to Steve Dower, Microsoft distributes an unsupported version for
> building Python 2.7 extension modules [1].
>
> 3.4 is built with the fairly old VS 2010, for which the free Express
> edition is no longer available. But you should be able to configure a
> command-line build environment. Install the Windows SDK 7.1 [2] and
> the VC++ 2010 SP1 Compiler Update [3]. Then run the Windows SDK 7.1
> Command Prompt [4], and enter
>
> SetEnv /Release /x64
>
> If you plan to do native debugging outside of Visual Studio, install
> the Debugging Tools for Windows [5] when installing the SDK. You can
> download public debug symbols for operating system components using
> Microsoft's symbol server. To do this, create a "C:\Symbols"
> directory, and set the following environment variable:
>
> _NT_SYMBOL_PATH=symsrv*symsrv.dll*C:\Symbols*
> http://msdl.microsoft.com/download/symbols
>
> Additionally you'll need Python's debug symbols, such as for 64-bit
> 3.4.3 [6]. I typically copy a PDB next to its related DLL/EXE. This is
> what 3.5's installer does when you select the option to install debug
> symbols (nice job, Steve!). You can also unzip the PDBs to a directory
> that's in _NT_SYMBOL_PATH, or update the symbol path dynamically using
> .sympath+ and .reload [7].
>
> [1]: https://www.microsoft.com/en-us/download/details.aspx?id=44266
> [2]: https://www.microsoft.com/en-us/download/details.aspx?id=8279
> [3]: https://www.microsoft.com/en-us/download/details.aspx?id=4422
> [4]: https://msdn.microsoft.com/en-us/library/ff660764
> [5]: https://msdn.microsoft.com/en-us/library/ff551063
> [6]: https://www.python.org/ftp/python/3.4.3/python-3.4.3.amd64-pdb.zip
> [7]: https://msdn.microsoft.com/en-us/library/ff565407
> --
> https://mail.python.org/mailman/listinfo/python-list
>
>
--
https://mail.python.org/mailman/listinfo/python-list
