please help! need to know python version
anna
Can anyone tell me what version of Python the latest version of Django
(and previous versions if available) is written/developed in? Or can
you tell me where I can find that info?
Thanks,
Anna
James Bennett
Django is compatible with any version of Python greater than 2.3, as
noted in the Django installation documentation:
http://www.djangoproject.com/documentation/install/
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
anna
2.3, 2.4 and 2.5 or just one of those? I know this is a weird
question, but I'm doing research for work and need to know this info.
The fact that it's just compatible with versions greater than 2.3 is
not enough - I need to know the exact version of Python the Django
code is written in.
Thanks,
Anna
On Jul 5, 10:19 am, "James Bennett" <ubernost...@gmail.com> wrote:
James Bennett
> 2.3, 2.4 and 2.5 or just one of those? I know this is a weird
> question, but I'm doing research for work and need to know this info.
> The fact that it's just compatible with versions greater than 2.3 is
> not enough - I need to know the exact version of Python the Django
> code is written in.
There is no "one version" in which Django is developed; different
developers have different installations with different versions of
Python, much the same as one developer might be writing code on Linux,
another on a Mac and yet another on a Windows machine (or, in a
Windows shop, one might have Vista, one XP and one Win2k). We check
compatibility by carefully reviewing the code and by running the test
suite against all three versions of Python we support (similarly, we
check database support by running the test suite against all of the
available database backends).
Tom Tobin
> > On 7/5/07, anna <uscbab...@gmail.com> wrote:
> >
> > > Can anyone tell me what version of Python the latest version of Django
> > > (and previous versions if available) is written/developed in? Or can
> > > you tell me where I can find that info?
> >
> > Django is compatible with any version of Python greater than 2.3, as
> > noted in the Django installation documentation:
> >
> > http://www.djangoproject.com/documentation/install/
>
> 2.3, 2.4 and 2.5 or just one of those? I know this is a weird
> question, but I'm doing research for work and need to know this info.
> The fact that it's just compatible with versions greater than 2.3 is
> not enough - I need to know the exact version of Python the Django
> code is written in.
I think you're asking an unanswerable question; Django is developed
*against* a particular minimum Python version's specification.
Someone could, in theory, hack on Django without ever touching a
Python interpreter (although I'd hope not, since running the test
suite is a Good Thing). ^_^ What version used alongside development
to test things will differ from developer to developer.
anna
Just in case anyone knows, is it the same with the other frameworks
for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
your answers here, but just wondering.
Thanks again,
Anna
Jeremy Dunck
>
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc?
Yes.
Why is the answer unfortunate? The answer is not bad-- the question
just has some bad assumptions built into it. Python is not compiled
until deployment, and compatibility on minor revs is very good.
How is it useful to know exactly which version something is if the
deployed code is plain text run in a compatible interpreter?
Tom Tobin
>
> On Jul 5, 10:42 am, "Tom Tobin" <korp...@korpios.com> wrote:
> >
> > I think you're asking an unanswerable question; Django is developed
> > *against* a particular minimum Python version's specification.
> > Someone could, in theory, hack on Django without ever touching a
> > Python interpreter (although I'd hope not, since running the test
> > suite is a Good Thing). ^_^ What version used alongside development
> > to test things will differ from developer to developer.
>
>
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
> your answers here, but just wondering.
Why is that answer troubling? I have the feeling there's a
misunderstanding going on here regarding what you're trying to
discover, and for what purpose.
Gary Doades
It's just that Django is compatible with Python versions 2.3, 2.4 and
2.5. I would have thought that was a good thing. It just means that you
can install any of the above versions of Python with the latest version
of Django and it will all work.
You would need to look at the other projects to get specific
information, but most of them are compatible with more than one version
of Python.
Regards,
Gary.
Don Arbow
> Django is compatible with any version of Python greater than 2.3, as
> noted in the Django installation documentation:
>
> http://www.djangoproject.com/documentation/install/
You mean >=, right? :-)
Don
Carl Karsten
wasn't an answer given, so not sure what answer you think you got.
Python code is not developed in Python. that can be debated, but for the
purposed of this thread, I think it fits.
That is like asking "what kind of car was your car developed in?" cars are
designed in offices, built in factories, driven on roads. granted software
development is a bit more integrated, it is also still separate. maybe a better
example would be "what brand of monitor was used?"
It would help if you explained the "research for work."
Carl K
James Bennett
> for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
> your answers here, but just wondering.
In the Python world, developing "against" a single specific version of
the language tends to be frowned upon; there's quite a lot of code out
there which runs compatibly on versions of Python from 1.5 through
2.5, and comparatively very little which is tied to a single specific
version of Python. Web framworks that I've seen tend to be upwards
compatible from 2.3 or 2.4, while in general a lot of Python software
aims for compatibility from 2.2 or 2.4, depending on what features
they need.
Is there a reason why you were hoping Django would somehow "favor" a
single specific version?
anna
our systems must be approved and only certain versions of Python are
approved for use/development (2.4 and possibly earlier ones, but I'm
not sure). We haven't yet chosen a framework to use for development
and it would be easier to get something approved if it was developed
against version(s) of Python already approved for our systems.
On Jul 5, 11:19 am, "James Bennett" <ubernost...@gmail.com> wrote:
Tom Tobin
> >
> > In the Python world, developing "against" a single specific version of
> > the language tends to be frowned upon; there's quite a lot of code out
> > there which runs compatibly on versions of Python from 1.5 through
> > 2.5, and comparatively very little which is tied to a single specific
> > version of Python. Web framworks that I've seen tend to be upwards
> > compatible from 2.3 or 2.4, while in general a lot of Python software
> > aims for compatibility from 2.2 or 2.4, depending on what features
> > they need.
> >
> > Is there a reason why you were hoping Django would somehow "favor" a
> > single specific version?
>
> our systems must be approved and only certain versions of Python are
> approved for use/development (2.4 and possibly earlier ones, but I'm
> not sure). We haven't yet chosen a framework to use for development
> and it would be easier to get something approved if it was developed
> against version(s) of Python already approved for our systems.
Django is made to work with Python 2.3 *and later*, as stated earlier
in this thread. If your organization uses Python 2.4, you won't have
a problem.
James Bennett
> our systems must be approved and only certain versions of Python are
> approved for use/development (2.4 and possibly earlier ones, but I'm
> not sure). We haven't yet chosen a framework to use for development
> and it would be easier to get something approved if it was developed
> against version(s) of Python already approved for our systems.
Then you have no problems here; Django will work on Python 2.4.
In a larger sense, it seems like you're confused about the Python
language; different versions of Python generally have good
compatibility with each other, which means that you don't have to
rewrite or recompile (in fact, you never "compile" Python code) when
moving between supported versions (e.g., you could "upgrade" or
"downgrade" your Python version without needing to change anything).
This is why we say Django is not developed "against" any single
version of Python -- because Python does a good job of maintaining
compatibility between versions, Django can run on any of Python 2.3,
2.4 or 2.5 without modification (and again, the Django test suite
verifies this).
Nicola Larosa
> Python code is not developed in Python.
You should talk to the PyPy guys/gals someday. ;-)
> that can be debated, but for the purposed of this thread, I think it
> fits.
Oh, you already took the above comment into account. :-)
--
Nicola Larosa - http://www.tekNico.net/
I accuse you, Mr. Bush, [...] of fomenting fear among your own people,
of creating the very terror you claim to have fought.
-- Keith Olbermann, July 2007
Nicola Larosa
>> Django is compatible with any version of Python greater than 2.3
Don Arbow wrote:
> You mean >=, right? :-)
Well, 2.3.6 is strictly greater than 2.3 . ;-)
http://www.python.org/download/releases/2.3.6/
Tai Lee
your approved list and therefore cannot run, you shouldn't have any
problems. django is built to work on python 2.3, just because it is
also compatible with 2.4 and 2.5 shouldn't mean anything. the fact
that the code still works on 2.4 and 2.5 is more likely a result of
the python developers maintaining backwards compatibility than django
developers designing django specifically to work on 2.4 and 2.5.
Steve Bergman
On Jul 5, 12:48 pm, anna <uscbab...@gmail.com> wrote:
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
> your answers here, but just wondering.
>
As someone coming to Django from TurboGears, I can say that TurboGears
tends to develop for one version of Python and then add support for
other versions as lesser supported afterthoughts.
It was originally developed for Python 2.4. When the topic of 2.3
support came up on the mailing list, the lead developers initial
response was "Hasn't everyone upgraded to 2.4?" It now has support
for 2.3, but it's really not tier one support, as TG makes such heavy
use of decorators.
Python 2.5 is now officially supported, but that is a recent
development.
As I have many clients on CentOS/RHEL, Django's equal treatment of
2.3, 2.4, and 2.5 is *greatly* appreciated.