Um, sorry, but this isn't correct.Although there might be a slight bit of gray area, the simple difference between compiled and interpreted languages is that compiled languages produce a binary consisting of bytes that mean something specific to the CPU of the computer the program is running on. Th
On 12 Oct 2005, at 09:33, bruno modulix wrote:
> Donn Cave wrote:
>
>> Quoth "Fredrik Lundh" <[EMAIL PROTECTED]>:
>> | Alex Stapleton wrote
>> |
>> | > Except it is interpreted.
>> |
>> | except that it isn't. Python source code is compiled to byte
>> code, which
>> | is then executed by a vir
Paul Boddie wrote:
> On the subject of other virtual machine implementations, I wonder what
> happened to this one:
>
> http://effbot.org/zone/pytte.htm
>
> Fredrik? ;-)
so much code, so little time...
--
http://mail.python.org/mailman/listinfo/python-list
Donn Cave wrote:
> Quoth "Fredrik Lundh" <[EMAIL PROTECTED]>:
> | Alex Stapleton wrote
> |
> | > Except it is interpreted.
> |
> | except that it isn't. Python source code is compiled to byte code, which
> | is then executed by a virtual machine. if the byte code for a module is up
> | to date, t
Alex Stapleton wrote:
>
> On 9 Oct 2005, at 19:04, Bruno Desthuilliers wrote:
>
>
>> Laszlo Zsolt Nagy a écrit :
(snip)
>>> Do you want to know how many internal string operations are done inside
>>> the Python interpreter? I believe it is not a useful information. There
>>> are benchmarks tes
Ognen Duzlevski wrote:
> I am curious, does this make a difference speed wise (aside
> from loading time)? The python tutorial would seem to imply
> that it does not:
>
> >From Python-Docs-2.4.2/tut/node8.html#SECTION00812
>
> "A program doesn't run any faster when it is read from
Donn Cave wrote:
> Quoth "Fredrik Lundh" <[EMAIL PROTECTED]>:
> | Alex Stapleton wrote
> |
> | > Except it is interpreted.
> |
> | except that it isn't. Python source code is compiled to byte code, which
> | is then executed by a virtual machine. if the byte code for a module is up
> | to date, t
Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Alex Stapleton wrote
> > Except it is interpreted.
> except that it isn't. Python source code is compiled to byte code, which
> is then executed by a virtual machine. if the byte code for a module is up
> to date, the Python runtime doesn't even look a
On Mon, 10 Oct 2005 11:21:18 -0700, Donn Cave <[EMAIL PROTECTED]>
wrote:
>> Iron-
>> Python). is it still an interpreter if it generates machine code?
>
> Is what an interpreter?
>
> I am not very well acquainted with these technologies, but it sounds
> like variations on the implementation of a
On Mon, 10 Oct 2005 16:47:35 -0700, Paul Boddie wrote:
>> The difficulty is that the target architecture in not realized in hardware.
>
> Or isn't perhaps feasible/viable for hardware realisation: one of the
> EuroPython speakers dangled the promise of hardware support for
> high-level languages
> Terry Hancock <[EMAIL PROTECTED]> (TH) wrote:
>TH> He's got to be talking about runtime name-binding. In
>TH> other words, when you refer to:
>TH> a.spam
>TH> the Python interpreter actually knows you labeled that attribute 'spam',
>TH> and the string is stored in a.__dict__ , so you can
Peter Hansen wrote:
> But I'm also not sure I ought to post that to the group, so I'll spare
> them and just inflict the thought on you!
Or, maybe I'll just fail to trim the newsgroup line and accidentally
post to the group anyway. Yes, that's just what I'll do.
Sorry folks. :-)
-Peter
--
ht
Steve Holden wrote:
> And we definitely need "agile" in there. Bugger, I'll go out and come in
> again ...
Used in the same breath as the word "bugger", I'm not sure the phrase
"go out and come in again" is entirely appropriate for a family forum. ;-)
But I'm also not sure I ought to post that
Peter Hansen wrote:
> Harald Armin Massa wrote:
>
>>"""
>>What is Python?
>>
>>Python is an interpreted, interactive, object-oriented programming
>>language. It is often compared to Tcl, Perl, Scheme or Java.
>>"""
>>taken from
>>http://www.python.org/doc/Summary.html
>>
>>maybe someone could upda
On Monday 10 October 2005 01:21 pm, Donn Cave wrote:
> In article <[EMAIL PROTECTED]>,
> I am not very well acquainted with these technologies, but it sounds
> like variations on the implementation of an interpreter, with no
> really compelling distinction between them. When a program is deployed
Harald Armin Massa wrote:
> """
> What is Python?
>
> Python is an interpreted, interactive, object-oriented programming
> language. It is often compared to Tcl, Perl, Scheme or Java.
> """
> taken from
> http://www.python.org/doc/Summary.html
>
> maybe someone could update that???
Maybe we shou
Donn Cave <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>, Mike Meyer <[EMAIL PROTECTED]>
> wrote:
>
>> Donn Cave <[EMAIL PROTECTED]> writes:
>> > I agree that there are many shades of grey here, but there's also a
>> > real black that's sharply distinct and easy to find -- real nativ
Dennis Lee Bieber wrote:
> I'd consider that BASIC to be a fully interpreted language, as the
> tokens are still a one-for-one equivalence of the source code. Python,
> UCSD, and Java are not one-for-one, so on that basis, they fit the
> definition of a compiled language...
That's an interesting d
In article <[EMAIL PROTECTED]>, Mike Meyer <[EMAIL PROTECTED]>
wrote:
> Donn Cave <[EMAIL PROTECTED]> writes:
> > I agree that there are many shades of grey here, but there's also a
> > real black that's sharply distinct and easy to find -- real native
> > code binaries are not interpreted.
>
>
Mike Meyer wrote:
> Donn Cave <[EMAIL PROTECTED]> writes:
>
>>I agree that there are many shades of grey here, but there's also a
>>real black that's sharply distinct and easy to find -- real native
>>code binaries are not interpreted.
>
>
> Except when they are. Many machines are microcoded, wh
On Saturday 08 October 2005 01:54 pm, Fredrik Lundh wrote:
> Dave wrote:
> > Yes, I would like to know how many internal string operations are done
> > inside
> > the Python interpreter.
>
> when you're doing what?
>
> how do you define "internal string operations", btw?
He's got to be talking
Donn Cave <[EMAIL PROTECTED]> writes:
> I agree that there are many shades of grey here, but there's also a
> real black that's sharply distinct and easy to find -- real native
> code binaries are not interpreted.
Except when they are. Many machines are microcoded, which means your
"real native co
Fredrik,
but still some very valuable people write:
"""
What is Python?
Python is an interpreted, interactive, object-oriented programming
language. It is often compared to Tcl, Perl, Scheme or Java.
"""
taken from
http://www.python.org/doc/Summary.html
maybe someone could update that???
Haral
In article <[EMAIL PROTECTED]>,
"Fredrik Lundh" <[EMAIL PROTECTED]> wrote:
> Donn Cave wrote:
>
> > | > Except it is interpreted.
> > |
> > | except that it isn't. Python source code is compiled to byte code, which
> > | is then executed by a virtual machine. if the byte code for a module is
Ditto to the below! I quite literally considered leaving the CS field until I found Python. Now my main job description is 'technical writing', but I get to use python at work (MoinMoin) and for all of my own computing needs.Cheers,KenOn 10-Oct-05, at 2:03 AM, Ron Adam wrote:If I was forced to go b
Steven D'Aprano wrote:
> For what it is worth, Python is compiled AND interpreted -- it compiles
> byte-code which is interpreted in a virtual machine. That makes it an
> compiling interpreter, or maybe an interpreting compiler, in my book.
Good points, and in addition to this, the individual byt
On Sun, 09 Oct 2005 21:00:57 +, Dennis Lee Bieber wrote:
> I'd consider that BASIC to be a fully interpreted language, as the
> tokens are still a one-for-one equivalence of the source code. Python,
> UCSD, and Java are not one-for-one, so on that basis, they fit the
> definition of a co
Donn Cave wrote:
> | > Except it is interpreted.
> |
> | except that it isn't. Python source code is compiled to byte code, which
> | is then executed by a virtual machine. if the byte code for a module is up
> | to date, the Python runtime doesn't even look at the source code.
>
> Fair to say t
Quoth "Fredrik Lundh" <[EMAIL PROTECTED]>:
| Alex Stapleton wrote
|
| > Except it is interpreted.
|
| except that it isn't. Python source code is compiled to byte code, which
| is then executed by a virtual machine. if the byte code for a module is up
| to date, the Python runtime doesn't even lo
Alex Stapleton wrote
> Except it is interpreted.
except that it isn't. Python source code is compiled to byte code, which
is then executed by a virtual machine. if the byte code for a module is up
to date, the Python runtime doesn't even look at the source code.
> What is your point?
that som
On 9 Oct 2005, at 19:04, Bruno Desthuilliers wrote:
> Laszlo Zsolt Nagy a écrit :
>
>
>> Dave wrote:
>>
>>
>>
>>> Hello All,
>>>
>>> I would like to gather some information on Python's runtime
>>> performance. As far as I understand, it deals with a lot of string
>>> objects. Does it require a l
Laszlo Zsolt Nagy a écrit :
> Dave wrote:
>
>> Hello All,
>>
>> I would like to gather some information on Python's runtime
>> performance. As far as I understand, it deals with a lot of string
>> objects. Does it require a lot string processing during program
>> execution? How does it handle
On Sat, 08 Oct 2005 10:14:25 -0700, Phillip J. Eby wrote:
> So, without meaning to, the benchmark author has demonstrated something
> important about Python, which is that writing the obvious thing in
> Python tends to work correctly, even if it sometimes takes longer to
> run than it would take f
Dave wrote:
> Yes, I would like to know how many internal string operations are done inside
> the Python interpreter.
when you're doing what?
how do you define "internal string operations", btw?
--
http://mail.python.org/mailman/listinfo/python-list
Paul Boddie wrote:
>> There are benchmarks testing the *real performance* of Python.
>>
>> For example: http://www.osnews.com/story.php?news_id=5602
>
> Just the observation that there are 166 comments to that article would
> suggest that the methodology employed was somewhat debatable. (I don't
>
Yes, I would like to know how many internal string operations are done inside the Python interpreter.
Thanks. Laszlo Zsolt Nagy <[EMAIL PROTECTED]> wrote:
Dave wrote:> Hello All,> > I would like to gather some information on Python's runtime > performance. As far as I understand, it deals with a
Laszlo Zsolt Nagy wrote:
> Dave wrote:
>
> > Hello All,
> >
> > I would like to gather some information on Python's runtime
> > performance. As far as I understand, it deals with a lot of string
> > objects. Does it require a lot string processing during program
> > execution? How does it handle su
Laszlo Zsolt Nagy wrote:
> There are benchmarks testing the *real performance* of Python.
>
> For example: http://www.osnews.com/story.php?news_id=5602
Just the observation that there are 166 comments to that article would
suggest that the methodology employed was somewhat debatable. (I don't
need
Dave wrote:
> Hello All,
>
> I would like to gather some information on Python's runtime
> performance. As far as I understand, it deals with a lot of string
> objects. Does it require a lot string processing during program
> execution? How does it handle such time-consuming operations? Is th
Hello All,
I would like to gather some information on Python's runtime performance. As far as I understand, it deals with a lot of string objects. Does it require a lot string processing during program execution? How does it handle such time-consuming operations? Is there a way to find out how m
> > Have u been used such camera with PIL before?
> >
> > im_1= Image.fromstring("I", datasize, buf, 'raw', 'I;16')
running on a 700 MHz box:
c:\> timeit -s "import Image" -s "data = 1344*1024*2*'x'"
"im = Image.fromstring('I', (1344, 1024), data, 'raw', 'I;16')"
10 loops, best of 3: 102 msec
> On 9/29/05, James Hu wrote:
> > Hi,
> >
> > I used python and PIL to capture image from a digital camera,
> > It seems like it took more than 1 second to capture a 1280x1024 image,
> > however, the demo capturing application from the company (coded by VB)
> > took only .2s or less for one image
You've gotta framinate your capacitor to speed it up.
(Translated: With no information about your camera, memory card, type
of connection, platform, method of access, version of python, version
of PIL, or code, how in the world could I help you to diagnose your
loosely-specified problem? Ask somet
Hi,
I used python and PIL to capture image from a digital camera,
It seems like it took more than 1 second to capture a 1280x1024 image,
however, the demo capturing application from the company (coded by VB)
took only .2s or less for one image with the same size.
Don't know why python and PIL is s
44 matches
Mail list logo
