Thank you, Pierre. I again apologize for asking extremely simple questions.
My interest in your WinPython distributions stems from my lack of success
using Cython in the past. I have always suspected that there is some sort
of minor configuration issue occurring that is preventing me from making
progress. Unfortunately I am still not having much success getting the
basic Cython tutorial to work (a simple "Hello World!";
http://docs.cython.org/src/userguide/tutorial.html), even when using
WinPython.
And I sincerely apologize if this question should be asked elsewhere, but
this seemed like a reasonable place to start given the goals of WinPython.
1) I have installed WinPython in "C:\WinPython-32bit-2.7.3.0". This
directory includes all of the links to Spyder, IPython, WPControlPanel, etc.
2) Using Spyder, I created the "helloworld.pyx" and "setup.py" files
indicated in the Cython tutorial. These file sit in a directory called
"C:\WinPython-32bit-2.7.3.0\python-2.7.3\myCython"
3) Still within Spyder, I used the "Tools" menu to open a command prompt
(it opens to the locations where my .pyx and setup.py file are located).
4) I issue the command
"python setup.py build_ext --inplace" at the prompt (as listed in the tutorial) and then see the following output:
running build_ext
cythoning hello.pyx to hello.c
building 'hello' extension
error: Unable to find vcvarsall.bat
I have searched my WinPython directory for the "vcvarsall.bat" file, and it
doesn't exist.
Does anyone have any suggestions?
Thanks,
-Mark
On Tuesday, September 25, 2012 11:42:22 AM UTC-7, Pierre Raybaut wrote:
> 2012/9/25 Mark <markper...@gmail.com <javascript:>>:
> > Sorry for asking what may be a very simple (or even technically
> incorrect)
> > question , but I am trying to get a little more information.
> > I was hoping that WinPython could possibly make my entry to using Cython
> a
> > little easier. I have not had much luck with Cython to date, and I know
> that
> > I am likely missing something simple. So I have downloaded WinPython to
> try
> > some things out and see if I can get Cython running under a more
> controlled
> > setting.
> > Does the distribution also contain all of the Python header files and
> code
> > required by Cython for compilation of cPython functions into modules?
> And is
> Yes for the 32-bit version of WinPython (MinGW32 with gcc is
> included), and no for the 64-bit version (you will have to install
> your own C compiler).
> > there a specific approach that is recommended for using Cython from
> > WinPython.
> No, WinPython is really close to a standard Windows Python
> installation. When running one of the launchers (.exe files at the
> root directory), the environment is exactly the same as the one you
> would have after installing Python with the official installer. So to
> run scripts installed with WinPython (like Cython) from a command
> window, you would have to run cmd.exe. But you can also run everything
> from Spyder: you write your .pyx script and build it in a terminal
> inside Spyder.
> > Also, when poking around in the python-2.7.3\Scripts folder, I see
> numerous
> > "*.bat" files that I don't have in my normal Python distribution. Is
> there
> > any information available regarding what these are used for?
> As I tried to explain in the readme.txt in that directory, these batch
> scripts are indeed specific to WinPython and they are only there to
> help the user eventually writing its own launchers. For example, the
> script "scripts\spyder.bat" does (almost) exactly the same things as
> the launcher "Spyder.exe". But none of this script is required for
> using WinPython, these are extras.
> > Sorry for cluttering the list with such basic questions, but thanks in
> > advance for any information that anyone can provide.
> No, problem.
> -Pierre
> > -Mark
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "WinPython" group.
> > To unsubscribe from this group, send email to
> > winpython+...@googlegroups.com <javascript:>.
> > For more options, visit https://groups.google.com/groups/opt_out.
