On Mon, Jan 6, 2014 at 9:55 PM, Chris Barker chris.bar...@noaa.gov wrote:
On Mon, Jan 6, 2014 at 12:26 PM, Steve Spicklemire st...@spvi.com wrote:
avoid troubling anyone with pesky questions. In that respect I've
apparently failed, because here comes the question!
I think this is a use
2014/1/7 PJ Eby p...@telecommunity.com
Probably yes, they would mind. ;-) I believe the reason there's a
space there is so that the file is not importable. (It should never
be imported; it's a data file rather than a python module.) I suspect
you'll have better luck with a suggestion like
On Wed, Jan 8, 2014 at 6:44 PM, Chris Barker chris.bar...@noaa.gov wrote:
On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau courn...@gmail.comwrote:
We don't use mingw to build packages distributed within canopy (at least
not anymore). We build everything with MSVC 2008, as mixing mingw/MSVC
This is good news. I'll experiment!
thanks,
-steve
On Jan 8, 2014, at 1:48 PM, David Cournapeau courn...@gmail.com wrote:
On Wed, Jan 8, 2014 at 6:44 PM, Chris Barker chris.bar...@noaa.gov wrote:
On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau courn...@gmail.com wrote:
We don't use
On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau courn...@gmail.com wrote:
We don't use mingw to build packages distributed within canopy (at least
not anymore). We build everything with MSVC 2008, as mixing mingw/MSVC
often causes trouble.
so is Canopy binary-compatible with the python.org
On 9 January 2014 04:44, Chris Barker chris.bar...@noaa.gov wrote:
On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau courn...@gmail.com wrote:
We don't use mingw to build packages distributed within canopy (at least
not anymore). We build everything with MSVC 2008, as mixing mingw/MSVC often
