On Apr 4, 5:48 pm, Robert Kern [EMAIL PROTECTED] wrote:
Mangabasi wrote:
Would Python 2.5 work with Visual Studio 6.6?
No.
--
Robert Kern
I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though
to
Fortran subroutines is strictly pass-by-reference. Thus the ain pointer.
Lenard Lindstrom
--
http://mail.python.org/mailman/listinfo/python-list
Howdy,
I have been trying to call the following Fortran function from Python
(using Windows XP, Compaq Fortran and Python 2.4). I tried F2Py,
Pyfort and calldll with no success.
I think I came very close with calldll. Here is a short summary
Fortran code:
SUBROUTINE SAMPLE(IERR1,IERR2
running config_fc
running build_src
building extension sample sources
creating /tmp/tmpZL8qAw
creating /tmp/tmpZL8qAw/src.macosx-10.3-fat-2.5
f2py options: []
f2py: sample.pyf
Reading fortran codes...
Reading file 'sample.pyf' (format:free)
Post-processing...
Block: sample
Steven D'Aprano [EMAIL PROTECTED] wrote:
On Mon, 26 Mar 2007 06:40:49 -0700, kyosohma wrote:
Fortran also appears to be a compiled language, whereas Python is an
interpreted language.
Sheesh. Do Java developers go around telling everybody that Java is an
interpreted language? I don't think so
at no charge. The Python
world is different from what experience with Fortran might
lead you to expect.
Your experience with Fortran is dated -- see below.
I'll be more clear: Fortran itself is a distinguished
language with many meritorious implementations. It can be
costly, though, finding
I feel obligated to fan the flames a bit by pointing to
http://www.fortranstatement.com/ a site which advocates discontinuing
development of Fortran and does a good job of summarizing the problems
with the contemporary development of that language.
I am not convinced that a new high performance
Tim Roberts [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
| Well, I'm being a bit argumentative here, but it's hard to deny that the
| use of compiled in the context of .pyc (or .javac) is very different
from
| the use of compiled in the context of running gcc.
Besides the fact
Terry Reedy wrote:
Tim Roberts [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
| Once upon a time,
| Basic enthusiasts would have used the word tokenized to describe .pyc
files.
Perhaps, but they would, I think, have been wrong. Tokenized Basic to the
best of my knowledge,
In article [EMAIL PROTECTED],
Beliavsky [EMAIL PROTECTED] wrote:
.
.
.
Your experience with Fortran is dated -- see below.
I'll be more clear: Fortran itself is a distinguished
language with many meritorious
On Mar 26, 12:59 pm, Erik Johnson [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad
Mark Morss wrote:
Maybe somebody reading this will be able to convince me to look again
at Numpy/Scipy, but for the time being I will continue to do my
serious numerical computation in Fortran.
What I am missing in this discussion is a link to Pyrex to speed up
Python: Pyrex is almost
On Mar 27, 12:55 pm, Jaap Spies [EMAIL PROTECTED] wrote:
Mark Morss wrote:
Maybe somebody reading this will be able to convince me to look again
at Numpy/Scipy, but for the time being I will continue to do my
serious numerical computation in Fortran.
What I am missing in this discussion
Steven D'Aprano [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Sheesh. Do Java developers go around telling everybody that Java is an
interpreted language? I don't think so.
What do you think the c in .pyc files stands for? Cheese?
On the contrary... Sun is very careful to make
In [EMAIL PROTECTED], Mark Morss
wrote:
Well, the discussion was about Python vs. Fortran, and Pyrex, as I
understand it, is a tool for linking C to Python.
I think it's more than that. It's more a subset of Python with a little
static typing.
Ciao,
Marc 'BlackJack' Rintsch
--
http
On Mar 27, 6:32 am, [EMAIL PROTECTED] (Cameron Laird) wrote:
In article [EMAIL PROTECTED],Beliavsky [EMAIL PROTECTED] wrote:
.
.
.
Your experience with Fortran is dated -- see below.
I'll be more clear: Fortran
On Tue, 27 Mar 2007 12:11:01 -0600, Erik Johnson wrote:
But seriously... I'm not a language or architecture guru. Is there any
real difference between a JVM and an interpreter? I mean, I have some
general feel that bytecode is a lower-level, more direct and more efficient
thing to be
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language nature, so what are the advantages of using Python for
creating number
On 26 Mar 2007 06:20:32 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
Python is hugely easier to read.
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran
On Mar 26, 8:20 am, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language
On Mar 26, 9:20 am, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language
On Mar 26, 3:20 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language
On Mar 26, 2:42 pm, Jean-Paul Calderone [EMAIL PROTECTED] wrote:
On 26 Mar 2007 06:20:32 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
Python is hugely easier to read.
quite useful in creating scientific apps
On 26 Mar 2007 06:47:18 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Mar 26, 2:42 pm, Jean-Paul Calderone [EMAIL PROTECTED] wrote:
On 26 Mar 2007 06:20:32 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read
You can get the speed of fortran in Python by using libraries like
Numeric without losing the readability of Python.
Can you back this up with some source??
Chris
Is this really the most important issue in your choice ?
As said by others, Portability, scalability RAD
On 26 Mar, 14:20, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
what are the advantages of using Python for
creating number crunching apps over Fortran??
If you have to ask, you've not experienced enough Fortran to know its
sheer horror.
You can write programs in Python that do usefully
On 26 Mar, 15:06, stef [EMAIL PROTECTED] wrote:
You can get the speed of fortran in Python by using libraries like
Numeric without losing the readability of Python.
Can you back this up with some source??
Chris
Is this really the most important issue in your choice ?
As said by others
On Mar 26, 4:47 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
You can get the speed of fortran in Python by using libraries like
Numeric without losing the readability of Python.
Can you back this up with some source??
Chris
If you execute one command in Python which tells a super
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
...
So I'ld suggest to start with downloading the Enthought edition of Python,
and you can judge for yourself within 10 minutes,
if it's fast enough.
cheers,
Stef Mientki
Is there a mac version??
In article [EMAIL PROTECTED],
Jean-Paul Calderone [EMAIL PROTECTED] wrote:
On 26 Mar 2007 06:20:32 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
Python is hugely easier to read.
quite useful in creating scientific
On 26 Mar 2007 06:20:32 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
On Mar 26, 10:11 am, Andy Dingley [EMAIL PROTECTED] wrote:
On 26 Mar, 14:20, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
what are the advantages of using Python for
creating number crunching apps over Fortran??
If you have to ask, you've not experienced enough Fortran to know its
sheer
On Mar 26, 3:20 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language nature, so
[EMAIL PROTECTED] a écrit :
On Mar 26, 8:20 am, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
.
.
.
You can get the speed of fortran in Python by using libraries like
Numeric without losing the readability of Python.
Can you back this up
with Fortran might
lead you to expect.
I'll be more clear: Fortran itself is a distinguished
language with many meritorious implementations. It can be
costly, though, finding the implementation you want/need
for any specific environment.
Python, in contrast, is blessed with a plethora
In article [EMAIL PROTECTED],
Alex Martelli [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
...
So I'ld suggest to start with downloading the Enthought edition of Python,
and you can judge for yourself within 10 minutes,
if it's fast enough.
cheers,
Stef Mientki
Alex Martelli wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
...
So I'ld suggest to start with downloading the Enthought edition of Python,
and you can judge for yourself within 10 minutes,
if it's fast enough.
cheers,
Stef Mientki
Is there a mac version??
On Mar 26, 9:42 am, Jean-Paul Calderone [EMAIL PROTECTED] wrote:
On 26 Mar 2007 06:20:32 -0700, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
Python is hugely easier to read.
quite useful in creating scientific apps
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language nature
On 26 Mar, 17:59, Erik Johnson [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad
To: python-list@python.org
Subject: Fortran vs Python - Newbie Question
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language
On Mon, 26 Mar 2007 06:40:49 -0700, kyosohma wrote:
Fortran also appears to be a compiled language, whereas Python is an
interpreted language.
Sheesh. Do Java developers go around telling everybody that Java is an
interpreted language? I don't think so.
What do you think the c in .pyc files
On Mar 26, 3:20 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than Fortran because of its a high level
language
On Mar 26, 8:40 am, [EMAIL PROTECTED] wrote:
On Mar 26, 8:20 am, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OK...
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
then Python is a tad slower than
of applications instead of focusing on numerical
functions like fortran does.
I wouldn't go as far as to say Python is a 'fast' language. But it's
certainly fun (particularly that), powerful, readable, and useful,
even for numerical computing.
Speed in numerical computing is a strange beast. First, a small
On Mar 26, 8:42 am, Jean-Paul Calderone [EMAIL PROTECTED] wrote:
snip
You can get the speed of fortran in Python by using libraries like
Numeric without losing the readability of Python.
Numeric and Numpy will faster than raw Python for array operations,
but I don't think they will match well
On Mon, 26 Mar 2007 15:53:56 -0700, sturlamolden wrote:
Python is a very high-level language. That means there are certain
things that put constraint on the attained speed. Most importantly:
keep the number of interpreter evals as scarce as possible. If you
make a for loop, the interpreter
On Mar 26, 9:06 am, stef [EMAIL PROTECTED] wrote:
As said by others, Portability, scalability RAD as an advantage of
Python are probably far more important.
All of those claimed advantages can be debated, although they may
exist for some tasks.
(1) Portability. Fortran has been run
On Mar 26, 10:31 am, Carl Banks [EMAIL PROTECTED] wrote:
snip
You can write programs in Python that do usefully complicated things,
and you can get them to work in a reasonable time. Fortran can't do
this, for anything more than the trivial. Classic Fortran tasks of
the past are now seen
On Mar 26, 10:16 am, [EMAIL PROTECTED] (Cameron Laird) wrote:
In article [EMAIL PROTECTED],[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Is there a mac version??
Thanks
Chris
Yes.
Several, in fact--all available at no charge. The Python
world is different from what experience with Fortran
Cameron Laird [EMAIL PROTECTED] wrote:
...
If you're just trying to learn and check things out, it might be better
to get a more recent Python from python.org (2.5 or 2.4.4) and the
various other packages as and when you need them (you can use the
MacEnthon list as a guide:-). You'll need
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I've been told that Both Fortran and Python are easy to read, and are
quite useful in creating scientific apps for the number crunching, but
Incidentally, and a bit outside what you asked: if your number
crunching involves anything beyond linear
Carl Banks wrote:
On Mar 26, 10:11 am, Andy Dingley [EMAIL PROTECTED] wrote:
On 26 Mar, 14:20, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
what are the advantages of using Python for
creating number crunching apps over Fortran??
If you have to ask, you've not experienced enough Fortran
in Fortran written data.
The data files are not binary, but ASCII text files with no formatting
and mixed data types (strings, integers, floats). For example, I have
the following write statements in my Fortran code:
I write the files as such:
WRITE(90,'(A30)') fgeo_name
WRITE(90,'(A30
getting acquainted with Python and, in particular SciPy,
NumPy, and Matplotlib. While I await the delivery of Travis Oliphant's
NumPy manual, I have a quick question (hopefully) regarding how to read
in Fortran written data.
The data files are not binary, but ASCII text files
[EMAIL PROTECTED] wrote:
I don't know if this is helpfull or not but (or for that matter
current). http://cens.ioc.ee/projects/f2py2e/ offers some suggestions
and it looks like you can use it with c code also.
f2py has been folded into numpy.
--
Robert Kern
I have come to believe that the
) regarding how to read
in Fortran written data.
The data files are not binary, but ASCII text files with no formatting
and mixed data types (strings, integers, floats). For example, I have
the following write statements in my Fortran code:
Konrad Hinsen has a module for reading this kind of file
) regarding how to read
in Fortran written data.
The data files are not binary, but ASCII text files with no formatting
and mixed data types (strings, integers, floats). For example, I have
the following write statements in my Fortran code:
In plain Python, you can read each line in to a string, break
) regarding how to read
in Fortran written data.
I think you made a good choice, if for no other reason than the fact
that Python and numpy absolutely rock when it comes to interfacing with
Fortran (and any C code that can be called by Fortran). I suggest
having a look at pyfort and/or f2py to see
Carl Banks wrote:
snip
WRITE(90,*) nfault,npoint
Fortran writes this as two arbitrary integers separated by a space.
I wrote a paragraph in my reply explaining why this is wrong. A Fortran
list-directed write can print results in an almost arbitrary format,
depending on the compiler
Beliavsky wrote:
Carl Banks wrote:
snip
WRITE(90,*) nfault,npoint
Fortran writes this as two arbitrary integers separated by a space.
I wrote a paragraph in my reply explaining why this is wrong.
It's a safe assumption for a line of two integers. It might not
exactly produce what
Carl Banks wrote:
snip
A Fortran
list-directed write can print results in an almost arbitrary format,
depending on the compiler. Many compilers will separate integers by
several spaces, not just one, and they could use commas instead of
spaces if they wanted.
1. Hardly any compiler
Beliavsky wrote:
Carl Banks wrote:
snip
A Fortran
list-directed write can print results in an almost arbitrary format,
depending on the compiler. Many compilers will separate integers by
several spaces, not just one, and they could use commas instead of
spaces if they wanted
for your replies, I think I even learnt
a few things about Fortran here too
Cheers,
t.
--
http://mail.python.org/mailman/listinfo/python-list
hello all,
i am currently in the process of planning a piece of software to model
polymerisation kinetics, and intend to use python for all the
high-level stuff. the number-crunching is something i would prefer to
do in fortran (which i have never used, but will learn), but i have no
experience
sam wrote:
hello all,
i am currently in the process of planning a piece of software to model
polymerisation kinetics, and intend to use python for all the
high-level stuff. the number-crunching is something i would prefer to
do in fortran (which i have never used, but will learn), but i
sam wrote:
hello all,
i am currently in the process of planning a piece of software to model
polymerisation kinetics, and intend to use python for all the
high-level stuff. the number-crunching is something i would prefer to
do in fortran (which i have never used, but will learn), but i
thanks guys,
i'll follow this up more in a couple of weeks when i know what i need
to do better.
sam
--
http://mail.python.org/mailman/listinfo/python-list
Hi all,
I'm currently working on a large, legacy Fortran application. I would
like to start new development in Python (as it is mainly I/O related).
In order to do so, however, the whole project needs to be able to
compile in Fortran.
I'm aware of resources like the F2Py Interface generator
unexpected schrieb:
I'm aware of resources like the F2Py Interface generator, but this only
lets me access the Fortran modules I need in Python. I'm wondering if
there's a way to generate the .o files from Python (maybe using
py2exe?) and then link the .o file with the rest of the Fortran
Hi!
in afternoon: http://calcul.math.cnrs.fr/article.php3?id_article=150
--
@-salutations
Michel Claveau
--
http://mail.python.org/mailman/listinfo/python-list
unexpected wrote:
Hi all,
I'm currently working on a large, legacy Fortran application. I would
like to start new development in Python (as it is mainly I/O related).
In order to do so, however, the whole project needs to be able to
compile in Fortran.
I'm aware of resources like
for
assembling applications from multiple parts, Python or otherwise.
See http://svn.zope.org/zc.buildout/trunk/.
- John Kimball will present a lightning talk of Fortran in Python.
- We will have a roundtable discussion of Python and Zope topics.
Gary
General
. The zc.buildout project provides support for creating
applications, especially Python applications. It provides tools for
assembling applications from multiple parts, Python or otherwise.
See http://svn.zope.org/zc.buildout/trunk/.
- John Kimball will present a lightning talk of Fortran
Ok, dennis, your solution may be better, but is quite dangerous:
Python can't handle if there is exactly 3 arguments passed to the
function. The created code is correct but the error will appear when
your run Fortran.
Cyril
On 7/9/05, Dennis Lee Bieber [EMAIL PROTECTED] wrote:
On Fri, 8 Jul
Dennis Lee Bieber wrote:
On 7/8/05, Einstein, Daniel R [EMAIL PROTECTED] wrote:
Hi,
Sorry for this, but I need to write ASCII from my Python to be read by
FORTRAN and the formatting is very important. Is there any way of doing
anything like:
write(*,'(3( ,1pe20.12
Title: FORTRAN like formatting
Hi,
Sorry for this, but I need to write ASCII from my Python to be read by FORTRAN and the formatting is very important. Is there any way of doing anything like:
write(*,'(3( ,1pe20.12))') (variable)
In other words, I want three columns 20 spaces long
Hello,
I don't anderstand very well Fortran syntax, but want you say
something like that:
def toTable(n1, n2, n3):
return %20s%20s%20s%tuple([%.12f%x for x in [n1, n2, n3]])
Example:
import math
toTable(math.pi, 10, 8.2323)
' 3.141592653590 10. 8.2323
while compiling on:
SunOS 5.8 Generic_108528-27 sun4u sparc SUNW,Sun-Fire-280R
I get the following error:
Undefined first referenced
symbol in file
matrixi_tst.o
ld: fatal: Symbol referencing errors. No output
This message was also posted and replied to on comp.lang.fortran -- I
think it's presence here is an accident.
--
http://mail.python.org/mailman/listinfo/python-list
Michael Tobis wrote:
Fortran programmers are generally happy with the portability of the
language.
Until they try to port something...? Honestly, I can't imagine where
anyone would get this impression.
From the fact that Fortran has been used on hundreds of platforms and
that many
Michael Tobis wrote:
[EMAIL PROTECTED] wrote:
Michael Tobis wrote:
Fortran 90/95 is more expressive than Fortran 77 in many ways, as
described in ...
http://www.nr.com/CiP97.pdf .
... expresses more science per
line of code and per programming workday.
The example shown on p 10
Hello,
I need to read a Fortran binary data file in Python.
The Fortran data file is organized thusly:
nx,ny,nz,ilog_scale # Record 1 (Header)
ihour,data3D_array# Record 2
Where every value above is a 2 byte Int. Further, the
first record is a header containing the dimensions of
the data
drife [EMAIL PROTECTED] writes:
I need to read a Fortran binary data file in Python.
The Fortran data file is organized thusly:
nx,ny,nz,ilog_scale # Record 1 (Header)
ihour,data3D_array# Record 2
Where every value above is a 2 byte Int.
Have you looked at the struct module?
http
301 - 385 of 385 matches
Mail list logo
