Fredrik Lundh wrote:
> Steve Holden wrote:
>
>>> for reference, here's what I get on Ubuntu 7.10, with the standard
>>> Python interpreter (2.5.1):
>>>
>>> $ python -c "import imp; print imp.get_suffixes()"
>>> [('.so', 'rb', 3), ('module.so', 'rb', 3), ('.py', 'U', 1),
>>> ('.pyc', 'rb', 2)]
>>>
llothar schreef:
>> There are ways to build distributions of Python extensions (modules or
>> packages involving binary code from languages like C or C++), but you
>> will want to understand a bit more about computing in general
>
> Believe me nobody needs to teach me anything about general progra
Steve Holden wrote:
>> for reference, here's what I get on Ubuntu 7.10, with the standard
>> Python interpreter (2.5.1):
>>
>> $ python -c "import imp; print imp.get_suffixes()"
>> [('.so', 'rb', 3), ('module.so', 'rb', 3), ('.py', 'U', 1),
>> ('.pyc', 'rb', 2)]
>>
>> any Ubuntu gurus here that c
Fredrik Lundh wrote:
> Fredrik Lundh wrote:
>
>> and for the record, Python doesn't look for PYD files on any of the Unix
>> boxes I have convenient access to right now. what Ubuntu version are
>> you using, what Python version do you have, and what does
>>
>> $ python -c "import imp; prin
> There must be a rule behind this.
There are multiple rules behind this. Python normally uses
the same extension for shared libraries as the operating
system, as the operating system may refuse to load them if
it doesn't. So it *can't* use .pyd on Unix, because that
might not work (on some implem
Fredrik Lundh wrote:
> and for the record, Python doesn't look for PYD files on any of the Unix
> boxes I have convenient access to right now. what Ubuntu version are
> you using, what Python version do you have, and what does
>
> $ python -c "import imp; print imp.get_suffixes()"
>
> pr
llothar wrote:
[...]
> Unfortunately there is no python.core mailing list that i know so i
> ask here.
>
Well your researches can't have been that extensive: the developers live
on [EMAIL PROTECTED], otherwise known as comp.land.python-dev. But
you will need to ask your question rather more care
llothar wrote:
> I don't think so. I asked a pretty simple question and as usual on
> usenet nobody read the question
did *you* read your own question? it took you three posts before you
mentioned what you were trying to do, and four posts before you bothered
to mention that you're seeing this
> Right, so you think people aren't trying to help you?
I think they are not reading the question.
> You display your ignorance here. The ".pyd" extension is used on Windows
> as an alternative to ".dll", but both are recognized as shared
> libraries. Personally I'm not really sure why they even
Steve Holden wrote:
> You display your ignorance here. The ".pyd" extension is used on Windows
> as an alternative to ".dll", but both are recognized as shared
> libraries. Personally I'm not really sure why they even chose to use
> ".pyd", which is confusing to most Windows users. In UNIX/Linu
llothar wrote:
> On 5 Apr., 15:48, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
>> llothar wrote:
>>> My question was: Why does setup.py generated sometimes a pyd and
>>> sometimes a so file?
>> setup.py picks an extension that happens to work on the platform you're
>> running setup.py on. doing other
llothar wrote:
> I ship an application that compiles an python interpreter and
> extension on a remote system.
> It also needs to copy this created items around. So if i use setup.py
> to create an
> extension i need to know the file name of the generated file.
so why not just ask setup.py
On 5 Apr., 15:48, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> llothar wrote:
> > My question was: Why does setup.py generated sometimes a pyd and
> > sometimes a so file?
>
> setup.py picks an extension that happens to work on the platform you're
> running setup.py on. doing otherwise would be pret
llothar wrote:
> My question was: Why does setup.py generated sometimes a pyd and
> sometimes a so file?
setup.py picks an extension that happens to work on the platform you're
running setup.py on. doing otherwise would be pretty pointless.
--
http://mail.python.org/mailman/listinfo/python-
Thanks, my question was not how can i make python to it find. I don't
have a problem.
My question was: Why does setup.py generated sometimes a pyd and
sometimes a so file?
There must be a rule behind this.
Unforunately setup.py is not well documented. Here i mean i need a
specification not a
tut
llothar wrote:
> On windows everything is '.pyd' but there seems to be two ways to get
> this on unix?
If you attempt to import the module "spam" on Windows, Python looks for
"spam.dll" and "spam.pyd" (in addition to "spam.py/spam.pyw/spam.pyc" etc)
On most Unix platforms, Python looks for "spa
On windows everything is '.pyd' but there seems to be two ways to get
this on unix?
Why and what is the rule?
--
http://mail.python.org/mailman/listinfo/python-list
17 matches
Mail list logo
