In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>The Doctor wrote:
>> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>>
>>>It turns out that the question isn't "How to install Python.h?
The Doctor wrote:
> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>
>>It turns out that the question isn't "How to install Python.h?" The
>>question is "Why doesn't make find Python.h?"
>>
>>---
In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>It turns out that the question isn't "How to install Python.h?" The
>question is "Why doesn't make find Python.h?"
>
>
It turns out that the question isn't "How to install Python.h?" The
question is "Why doesn't make find Python.h?"
# uname -v
FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014
#
In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>In article you wrote:
>> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>>
>>>The installed python packages are shown below. Searches lead me to
>>>believe that a PTH option make play a role.
>>>
>>>--
In article you wrote:
> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>
>>The installed python packages are shown below. Searches lead me to
>>believe that a PTH option make play a role.
>>
>>
>>$ uname -v
>>FreeBSD
In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>The installed python packages are shown below. Searches lead me to
>believe that a PTH option make play a role.
>
>
>$ uname -v
>FreeBSD 10.0-RELEASE #0 r260789: Thu Jan
The installed python packages are shown below. Searches lead me to
believe that a PTH option make play a role.
$ uname -v
FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/
On Mon, Jan 30, 2012 at 2:34 AM, Andrea Crotti
wrote:
> I have a newbie question about CPython.
> Looking at the C code I noted that for example in tupleobject.c there is
> only one include
> #include "Python.h"
For files like tupleobject.c there's often a corresp
d put the extern block around the #include call
rather than individual functions, as surely the C calling convention
should apply to everything within.
makes it look way too much like "this is how you should use python.h" to
be appropriate, given the earlier discussions in the thr
On Jul 23, 1:19 pm, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Ben Sizer wrote:
> > You should put the extern block around the #include call
> > rather than individual functions, as surely the C calling convention
> > should apply to everything within.
>
> Hello? Python's include files are C++ sa
> 1>application.obj : error LNK2031: unable to generate p/invoke for
> "extern "C" void __clrcall Py_Exit(int)" (?Py_Exit@@[EMAIL PROTECTED]);
> calling convention missing in metadata
The main problem here is the __clrcall hint: apparently, you are
using Managed C++ resp. C++/CLI, i.e. the Microso
Jaco Naude wrote:
Fredrik, thanks for the help. I'm not sure why but it seems to work
now even if I don't include the extern "C" command. It also works with
both Python.h files (after I copied pyconfig.h from the PC folder). So
it seems like everything is working now.
As
ed to specify that you're not with this DLL, though I've never
> had to deal with anything like that myself.
>
> --
> Ben Sizer
Fredrik, thanks for the help. I'm not sure why but it seems to work
now even if I don't include the extern "C" command. It also
Ben Sizer wrote:
You should put the extern block around the #include call
rather than individual functions, as surely the C calling convention
should apply to everything within.
Hello? Python's include files are C++ safe. I even posted a complete
compiler session to show that I'm not makin
On Jul 23, 11:43 am, Jaco Naude <[EMAIL PROTECTED]> wrote:
> What Visual C++ is doing is that it is looking for mangled names since
> it does not know the DLL contains C functions. I've managed to work
> around this by declaring the Python functions as follows before using
> them in the C++ applica
> > }
>
> > > This seems to work and the C++ application side is not looking for
> > > mangled names any more. Is this the right way of doing it? It seems
> > > unnecessary to have to declare each Python function you want to use
> > > using the extern &quo
Jaco Naude wrote:
That said, let me double check something which might be causing
problems since you will be familiar with this. Which Python.h file do
you include when including the DLL in your programs? The one in the
source distribution of the one in the installation distribution? I've
Is this the right way of doing it? It seems
> > unnecessary to have to declare each Python function you want to use
> > using the extern "C" way as shown above.
>
> Eh, are you saying that you're not including the Python.h file? Because
> it does exactly that
Fredrik Lundh wrote:
> cl cl -EHsc -MD -I \python25\include test.cc \python25\libs\python25.lib
cut and paste error there: the "cl cl" should be just one "cl", of course.
and just for the record/google, if I
1) don't include the header file, I get
test.cc(5) : error C3861: 'Py_Initialize':
ou saying that you're not including the Python.h file? Because
it does exactly that, for each and every public function in the C API.
It is probably more of a C++ question it turns out, but I would think
that someone in the Python group would use the Python DLL in C++. The
documentation also
e DLL using Dependency Walker and the
> > functions in the DLL are clean (Thus no name mangling used).
>
> > How do I tell Visual C++ that the DLL is a C dll? I thought it should
> > be in Python.h but this line appears at the top of the file:
>
> > /* Since t
>
How do I tell Visual C++ that the DLL is a C dll? I thought it should
be in Python.h but this line appears at the top of the file:
/* Since this is a "meta-include" file, no #ifdef __cplusplus / extern
"C" { */
All the individual includes are wrapped in the usual
> calling convention missing in metadata
> > 1>frmPythonInterface.obj : error LNK2031: unable to generate p/invoke
> > for "extern "C" void __clrcall Py_Exit(int)" (?Py_Exit@@[EMAIL PROTECTED]);
> > calling convention missing in metadata
>
> > I'm probably missin
nvoke
for "extern "C" void __clrcall Py_Exit(int)" (?Py_Exit@@[EMAIL PROTECTED]);
calling convention missing in metadata
I'm probably missing something but I can't find any calling convention
details in Python.h or the other headers included in this file.
the precen
d folder of the source
download and this works 100% without any warnings etc. I've done this
in Debug and Release mode without any problems.
When I include python_install_path\include\Python.h in my application
(with the linking setup correctly to the .lib and .dll files generated
by myself) it bui
Raj kumar wrote:
> Hi to all,
> I'm new to Python.
> I am using python2.4.
> I have one application written in c language in which it includes python like
>
> #include "Python.h"
>
> But when i try to install it, i'm getting an error like
> Pyth
Hi to all,
I'm new to Python.
I am using python2.4.
I have one application written in c language in which it includes python like
#include "Python.h"
But when i try to install it, i'm getting an error like
Python.h: No such file or directory
I feel gcc is unable to get the pa
"Marcelo Gosling" <[EMAIL PROTECTED]> wrote:
>
>Hi, everyone.
>
>This is on WinXP SP2, with Python 2.4.3 and DJGPP gcc 4.1.0.
>
>I'm having trouble including Python.h in a C file. The following C
>code:
>
>#include "Python.h"
>
&
On 24/06/2006 12:14 PM, John Machin wrote:
> On 24/06/2006 7:51 AM, Marcelo Gosling wrote:
>> I'm having trouble including Python.h in a C file. The following C
>> code:
>> In file included from ../../Python2.4/include/Python.h:74,
>> from
On 24/06/2006 7:51 AM, Marcelo Gosling wrote:
> Hi, everyone.
>
> This is on WinXP SP2, with Python 2.4.3 and DJGPP gcc 4.1.0.
>
> I'm having trouble including Python.h in a C file. The following C
> code:
>
> #include "Python.h"
>
> int main()
&g
No, that didn't do the trick. The main reason I'm posting this here is
that I get all tese error messages just from including Python.h, the
code itself does absolutely nothing.
Cheers
vduber6er wrote:
> Try
>
> #undef _DEBUG
> #include "C:\Python24\include\python.h&q
Try
#undef _DEBUG
#include "C:\Python24\include\python.h"
or which ever path your python.h is located at
works for me
Marcelo Gosling wrote:
> Hi, everyone.
>
> This is on WinXP SP2, with Python 2.4.3 and DJGPP gcc 4.1.0.
>
> I'm having trouble including Python.
Hi, everyone.
This is on WinXP SP2, with Python 2.4.3 and DJGPP gcc 4.1.0.
I'm having trouble including Python.h in a C file. The following C
code:
#include "Python.h"
int main()
{
return 0;
}
when compiled with "gcc -I..\Python2.4\include\", gives more
[EMAIL PROTECTED] wrote:
> I am running python to c converter application. It throws an
> error saying python.h file not found.
>Can somebody plz suggest how to resolve this problem.
you need the python build files. if you're using Linux, look for
something named
Hi,
I am running python to c converter application. It throws an
error saying python.h file not found.
Can somebody plz suggest how to resolve this problem.
Regards,
Praveen Kumar
--
http://mail.python.org/mailman/listinfo/python-list
Andrew MacIntyre wrote:
> My suspicion would be directed to a #define that is incorrect, as the
> snippet above suggests that select() appears in two system headers
> (/usr/include/sys/time.h & /usr/include/unistd.h).
thanks for the info.
I need to undef the following from my pyconfig.h to make i
Bram Stolk wrote:
> Hi there,
>
> I just built and installed Python-2.4.1 on my Irix machine.
> My compiler, the MipsPro compiler, chokes on the Python.h include file,
> as demonstrated here:
>
>
> $ CC -v
> MIPSpro Compilers: Version 7.41
> $ python -V
> Pyth
Dennis Lee Bieber wrote:
> On Tue, 24 May 2005 13:20:01 +0200, Bram Stolk <[EMAIL PROTECTED]>
> declaimed the following in comp.lang.python:
>
>
>>$ cat l.cxx
>
>
> Isn't ".cxx" a "C++" indicator? I think Python is just plain C,
> so you'd have to wrap everything to indicate C style namin
Hi there,
I just built and installed Python-2.4.1 on my Irix machine.
My compiler, the MipsPro compiler, chokes on the Python.h include file,
as demonstrated here:
$ CC -v
MIPSpro Compilers: Version 7.41
$ python -V
Python 2.4.1
$ cat l.cxx
#include
int main()
{
return 0;
}
$ CC -I $HOME
>
> It *should* be
> /System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3/Python.h
>
> In the meantime, you can snag a pre-built Numeric from
>
>http://pythonmac.org/packages/
It was not there to start with and by trying to install xcode from
app
Frameworks/vecLib.framework/Headers
-IInclude -IPackages/FFT/Include -IPackages/RNG/Include
-I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3
-c Src/arrayobject.c -o
build/temp.darwin-7.8.0-Power_Macintosh-2.3/Src/arrayobject.o
Src/arrayobject.c:18:20: Python.h: No such file or directo
ework/Headers
-IInclude -IPackages/FFT/Include -IPackages/RNG/Include
-I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3
-c Src/arrayobject.c -o
build/temp.darwin-7.8.0-Power_Macintosh-2.3/Src/arrayobject.o
Src/arrayobject.c:18:20: Python.h: No such file or directory
In file
43 matches
Mail list logo
