XP) - but if you could use the MySQLdb module for Python 2.4, i'd suspect
> that you probably got the wrong module? There is one specifically for Python
> 2.5 on the Sourceforge download page. Also, maybe check that you chose the
> correct version (64-bit or 32-bit) depending on your ins
Hi Eric,
I am not sure that the problem you experienced is related to Windows 7 (am
on XP) - but if you could use the MySQLdb module for Python 2.4, i'd suspect
that you probably got the wrong module? There is one specifically for Python
2.5 on the Sourceforge download page. Also, maybe
Thank you.
Unfortunately, it hasn't worked for me; been there a few times in my
searches :(
For others finding this I could not get MySQLdb to work on Windows 7
with Python 2.5 but have managed to get it to work with Python 2.4.
On Dec 23, 6:19 am, OkaMthembo wrote:
> Correction: i
Correction: it was an installer, not package, that i downloaded.I went with
the .exe, which extracts the MySQLdb module into the relevant site-packages
folder of your Python installation.
Lloyd
On Wed, Dec 23, 2009 at 4:12 PM, OkaMthembo wrote:
> Hi Eric,
>
> Apologies, i can't seem to find the
Correction: that was a module that i downloaded, not a package.
On Wed, Dec 23, 2009 at 4:12 PM, OkaMthembo wrote:
> Hi Eric,
>
> Apologies, i can't seem to find the exact thread (it was in response to
> someone else's enquiry). However, i do remember that i downloaded the
> MySQLdb package from
Hi Eric,
Apologies, i can't seem to find the exact thread (it was in response to
someone else's enquiry). However, i do remember that i downloaded the
MySQLdb package from this link:
http://sourceforge.net/projects/mysql-python/files/
Expand the mysql-python folder and expand the 1.2.2. folder.
setuptools
2009/12/23 ericvb
> Can you point to that thread please? I've searched but can't find it.
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscr
Can you point to that thread please? I've searched but can't find it.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-user
page, i'm getting an
>> error: "*Error loading MySQLdb module: no module named MySQLdb*"
>>
>> I then Googled about and found the modules at Sourceforge. There does not
>> seem to be a 32bit one for Python 2.5 - please advise? I am also wondering
>> whe
gs file and reloaded the Django welcome page, i'm getting an
> error: "*Error loading MySQLdb module: no module named MySQLdb*"
>
> I then Googled about and found the modules at Sourceforge. There does not
> seem to be a 32bit one for Python 2.5 - please advise? I am als
les at Sourceforge. There does not
seem to be a 32bit one for Python 2.5 - please advise? I am also wondering
whether the module should be unzipped into the MySQL bin folder (tried that
with the 64 bit one and aded the bin folder to the PATH variable. No
success).
--
Regards,
Sithembewena Lloyd
On Nov 4, 2009, at 4:01 AM, joker wrote:
>
> i update python 2.5.2 to 2.6 and setup changed directory
> /usr/lib/python2.5 to /usr/local/lib/python2.5/
That doesn't look right. If you installed 2.6, the new directories
should have 2.6 in them, not 2.5 and so should your tracebacks.
S
> a
i worked easy_install mysql-python command but still doesnt work
On 4 Kasım, 11:17, Roland van Laar wrote:
> joker wrote:
> > i update python 2.5.2 to 2.6 and setup changed directory
> > /usr/lib/python2.5 to /usr/local/lib/python2.5/
> > and django doesnt working now
>
> > ImproperlyConfigured
joker wrote:
> i update python 2.5.2 to 2.6 and setup changed directory
> /usr/lib/python2.5 to /usr/local/lib/python2.5/
> and django doesnt working now
>
> ImproperlyConfigured: Error importing middleware
> django.contrib.flatpages.middleware: "No module named mysql.base"
>
You might want t
Looks like your python 2.5 had the python mysql packages installed, but
your new python 2.6 doesn't, which it wouldn't being a fresh install.
Now you need to install the python mysql bindings into python 2.6.
Also, you should probably have your libs in for python 2.6
in /usr/local/lib
i update python 2.5.2 to 2.6 and setup changed directory
/usr/lib/python2.5 to /usr/local/lib/python2.5/
and django doesnt working now
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line
1537, in HandlerDispatch
File "/usr/lib/python2.5/s
yes, and it contains the jpg and gif plugins, which I assume means
that it does support jpgs.
On Jul 27, 9:15 pm, Darryl Ross wrote:
> Cody Django wrote:
> > ImageFields worked just fine until I moved to a new server. Now I get
> > error messages "Upload a valid image". I know the images are
checked:
- pil supports jpgs
- permissions set to 775 on upload folders
On Jul 27, 7:44 pm, Cody Django wrote:
> All imagefields give this error: Upload a valid image. The file you
> uploaded was either not an image or a corrupted image.
>
> I suspect that imagefield itself is compatible with p
Cody Django wrote:
> ImageFields worked just fine until I moved to a new server. Now I get
> error messages "Upload a valid image". I know the images are fine,
> the media root and www_url are correct, so what else could this be?
> Ideas are greatly appreciated!
Do you have PIL installed on the
All imagefields give this error: Upload a valid image. The file you
uploaded was either not an image or a corrupted image.
I suspect that imagefield itself is compatible with python 2.3, so
where else could the problem be? It's not with the image.
Ideas are greatly appreciated... Thanks.
--~--
ImageFields worked just fine until I moved to a new server. Now I get
error messages "Upload a valid image". I know the images are fine,
the media root and www_url are correct, so what else could this be?
Ideas are greatly appreciated!
Cody
--~--~-~--~~~---~--~~
On Wed, Jun 17, 2009 at 12:44 PM, Shuge Lee wrote:
>
> Does Django have to run with Python-2.5 ?
>
>
> l...@lab ~/online $ python2.6 manage.py runserver
> Traceback (most recent call last):
> File "manage.py", line 2, in
>from django.core.management import
Does Django have to run with Python-2.5 ?
l...@lab ~/online $ python2.6 manage.py runserver
Traceback (most recent call last):
File "manage.py", line 2, in
from django.core.management import execute_manager
ImportError: No module named django.core.management
l...@la
On Wed, Jun 17, 2009 at 11:44 AM, Shuge Lee wrote:
>
> Does Django have to run with Python-2.5 ?
>
>
> l...@lab ~/online $ python2.6 manage.py runserver
> Traceback (most recent call last):
> File "manage.py", line 2, in
>from django.core.management import
Does Django have to run with Python-2.5 ?
l...@lab ~/online $ python2.6 manage.py runserver
Traceback (most recent call last):
File "manage.py", line 2, in
from django.core.management import execute_manager
ImportError: No module named django.core.management
l...@la
On Mar 30, 7:45 pm, Karen Tracey wrote:
> On Mon, Mar 30, 2009 at 7:24 PM, Mitch wrote:
>
> > With django 1.0.2 and Python 2.5, when I use the keyword
> > DateField.input_formats, I get the error that __init__() got an
> > unexpected keyword argument 'input
On Mar 30, 7:45 pm, Karen Tracey wrote:
> On Mon, Mar 30, 2009 at 7:24 PM, Mitch wrote:
>
> > With django 1.0.2 and Python 2.5, when I use the keyword
> > DateField.input_formats, I get the error that __init__() got an
> > unexpected keyword argument 'input
On Mar 30, 7:45 pm, Karen Tracey wrote:
> On Mon, Mar 30, 2009 at 7:24 PM, Mitch wrote:
>
> > With django 1.0.2 and Python 2.5, when I use the keyword
> > DateField.input_formats, I get the error that __init__() got an
> > unexpected keyword argument 'input
On Mon, 2009-03-30 at 19:48 -0400, Karen Tracey wrote:
> On Mon, Mar 30, 2009 at 7:40 PM, Malcolm Tredinnick
> wrote:
> Presumably you are talking about calling the constructor of
> forms.DateField here, since you don't mention what __init__
> method you
> are call
On Mon, Mar 30, 2009 at 7:40 PM, Malcolm Tredinnick <
malc...@pointy-stick.com> wrote:
> Presumably you are talking about calling the constructor of
> forms.DateField here, since you don't mention what __init__ method you
> are calling. Support for the input_formats argument to
> DateField.__init_
On Mon, Mar 30, 2009 at 7:24 PM, Mitch wrote:
>
> With django 1.0.2 and Python 2.5, when I use the keyword
> DateField.input_formats, I get the error that __init__() got an
> unexpected keyword argument 'input_formats'. When I look in the
> __init__ definition, I don
On Mon, 2009-03-30 at 16:24 -0700, Mitch wrote:
> With django 1.0.2 and Python 2.5, when I use the keyword
> DateField.input_formats, I get the error that __init__() got an
> unexpected keyword argument 'input_formats'. When I look in the
> __init__ definition, I don't
With django 1.0.2 and Python 2.5, when I use the keyword
DateField.input_formats, I get the error that __init__() got an
unexpected keyword argument 'input_formats'. When I look in the
__init__ definition, I don't see input_formats as one of the
acceptable keyword arguments.
Have you tried Macports? If not, you should check it out.
On Oct 20, 2:11 pm, Francis <[EMAIL PROTECTED]> wrote:
> I had trouble installing PIL on my Mac with 10.5 Leopard.
>
> I always got an : "Upload a valid image. The file you uploaded was
> either not an image
> or a corrupted image."
>
> I
I had trouble installing PIL on my Mac with 10.5 Leopard.
I always got an : "Upload a valid image. The file you uploaded was
either not an image
or a corrupted image."
I searched to groups for answer but it seems that others were also
having this problem.
For those who are still looking for a s
Whoops, sorry, ignore that last...
On Nov 1, 10:16 am, [EMAIL PROTECTED] wrote:
> Ulf, did you ever figure this out? I don't use pgsql/psycopg, but I've
> had the same issues with mod_python and competing framework/MacPort
> installations of Python. And I didn't even know there was a
> $PYTHONHOM
Ulf, did you ever figure this out? I don't use pgsql/psycopg, but I've
had the same issues with mod_python and competing framework/MacPort
installations of Python. And I didn't even know there was a
$PYTHONHOME variable.
I've done everything I can to change paths and reroute framework-
Python to
Very sorry, I wasn't having the problem I thought I was having. I
still don't know why the traceback was switching to the old
installation of Python, but at any rate the real problem was that it
couldn't find the settings module - my DJANGO_SETTINGS_MODULE and
PythonPath had an overlapping file-pa
I had everything (Apache, mysql, mod_python etc) installed through
macports but was still using Python from the built-in framework. That
was giving me trouble, so I tried to switch over to using the
macports Python installation, which came down as a dependency for
Apache/mod_python.
Needle
On 26 Oct 2007, at 2:37 am, Kristinn Örn Sigurðsson wrote:
> Sorry if I wasn't clear about what I was talking about. :-)
>
> I'm using Darwin ports. They work similar to BSD ports (completely
> different but the idea is probably from there). With that you can
> install alot of *nix applicati
f Django and it just worked. :-)
Hope this helps.
Kristinn.
On 10/26/07, Matthew Wensin <[EMAIL PROTECTED]> wrote:
>
> Can you elaborate on "just install and update your python version through
> ports and install everything you need from there"?
>
> I'm using P
Can you elaborate on just install and update your python version through
ports and install everything you need from there?
Im using Python 2.5 (from here: http://pythonmac.org/packages/)--do you
mean Python 2.5.1?
Matt
On 10/25/07 9:09 PM, "Kristinn Örn Sigursson"
<[EMAIL PROT
That's too much of a hack when you can just install and update your python
version through ports and install everything you need from there, without
touching the MacOSX system itself. I guess you can use /usr/local without
destroying the OSX, but still... I think the ports way is better. :-)
Just m
I've dealt with that exact error before, just yesterday, incidentally. What
I did to fix:
$ locate libpq.5
If this returns nothing, try running:
$ sudo /usr/libexec/locate.updatedb
And then $ locate libpq.5 again.
Go to the directory containing libpq.5 (for me it was /usr/local/pgsql/lib,
an
I'm sorry. I'm using version 1 of psycopg. If I fire up a python shell I can
import it as "import psycopg". Hope that helps.
On 10/25/07, Francis Lavoie <[EMAIL PROTECTED]> wrote:
>
>
> have you tried to import the module into python directly?
>
>
>
> Le 07-10-25 à 18:58, Frank a écrit :
>
> >
> >
have you tried to import the module into python directly?
Le 07-10-25 à 18:58, Frank a écrit :
>
> All-
>
> Having a rough go getting database bindings in OS X.
>
> I've installed psycopg2 using the package here:
> http://pythonmac.org/packages/py25-fat/mpkg/psycopg2-2.0.5.1-py2.5-
> macosx10
I recommend to use Darwin ports or fink to do that. I used Darwin ports on
my mac and it works perfectly.
On 10/25/07, Frank <[EMAIL PROTECTED]> wrote:
>
>
> All-
>
> Having a rough go getting database bindings in OS X.
>
> I've installed psycopg2 using the package here:
>
> http://pythonmac.org/p
All-
Having a rough go getting database bindings in OS X.
I've installed psycopg2 using the package here:
http://pythonmac.org/packages/py25-fat/mpkg/psycopg2-2.0.5.1-py2.5-macosx10.4.zip
When I run 'python manage.py shell' I get the following... any ideas
on how to fix this?
Traceback (most r
> That one has to go to the
> extent of reading the Python source code to fully understand what it
> is for is a good sign that the typical user shouldn't be using it for
> anything. If it is there for any reason, I'd say it is more for people
> who are tinkering with the actual Python code itself
On Oct 22, 3:01 pm, Ulf Kronman <[EMAIL PROTECTED]> wrote:
> Hi Graham,
>
> > You should not need to set PYTHONHOME and doing so could cause a lot
> > of problems because if you now run /usr/bin/python2.3 directly or
> > indirectly, it will pick up the wrong installed version of Python
> > modules
Hi Graham,
> You should not need to set PYTHONHOME and doing so could cause a lot
> of problems because if you now run /usr/bin/python2.3 directly or
> indirectly, it will pick up the wrong installed version of Python
> modules.
OK, I'll remove it. But why should I want to run Python 2.3? As I h
On Oct 22, 5:36 am, Ulf Kronman <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> > Have you made any try on Python 2.5 together with mod_python?
>
> I'll reply to myself here, since I finally got mod_python to work with
> Python 2.5!
>
> Here's how I did it:
Hi all,
> Have you made any try on Python 2.5 together with mod_python?
I'll reply to myself here, since I finally got mod_python to work with
Python 2.5!
Here's how I did it:
--
Installed Python 2.5.1 from the DMG package.
Set up paths in my ~/.profile
y come from...
OK, it seems as if you have come to the same conclusion as I - that
it's safest to install the Python DMG versions and compile packages by
hand. It's a pity, since MacPorts is very convenient, when it works.
Have you made any try on Python 2.
Hi again Graham,
> No, that is a different flag. It is -Wl,-f not -Wl,-F. They mean
> different things. You would use:
>
> LDFLAGS = -Wl,-F/Library/Frameworks .existing options
OK, I understand. The -F option is just to point to the right
framework location.
But my previous compilation/ins
mand I used:
> ./configure --with-apxs=/opt/local/apache2/bin/apxs --with-python=/
> Library/Frameworks/Python.framework/Versions/2.4/bin/python
>
> When I did my trials with Python 2.5, I also pointed at that version
> in the compilation, but still got a mod_python that said it wa
on to use.
>
> Yes, I did point at my Python 2.4. Here is the config command I used:
> ./configure --with-apxs=/opt/local/apache2/bin/apxs --with-python=/
> Library/Frameworks/Python.framework/Versions/2.4/bin/python
>
> When I did my trials with Python 2.5, I also pointed at t
/apxs --with-python=/
Library/Frameworks/Python.framework/Versions/2.4/bin/python
When I did my trials with Python 2.5, I also pointed at that version
in the compilation, but still got a mod_python that said it was
compiled for running Python 2.4 as a result.
> 3. Often with MacPorts versions of
.
Graham
On Oct 19, 11:59 pm, Ulf Kronman <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have severe problems to get my Apache 2 to run mod_python together
> with Python 2.5 on Mac OS X 10.4.10.
>
> This is my sad story:
>
> I'm developing a small in-house publicati
Hi all,
I have severe problems to get my Apache 2 to run mod_python together
with Python 2.5 on Mac OS X 10.4.10.
This is my sad story:
I'm developing a small in-house publication database for bibliometric
purposes. I run a Ubuntu Linux-based server with Apache, Python and
PostgreSQL,
hi,
I have a bunch of sites in production running on python 2.4.x.
Recently I set up a new desktop with mandriva2007 and set up my sites
on the local machine with python 2.5, apache2.2 and mod_python 3.3.1.
The directory setup and files were taken directy from the svn
checkouts of the
I have to install Django for a project and i have to install FastCGI
for testing a application on my computer.
I have install Python 2.5, Django ,mod_python, Apache2.0.
For FastCGI and SCGI i have install flup and i get flup
http://trac.saddi.com/flup,
there stand i have to install eunuchs if i
On Jul 20, 4:50 am, lars <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> yesterday I tried to install django on my macbook. Since I wanted to
> have a more recent python interpreter I installed the one from
> macports.
> There's a pitfall, however. Because in order to get MD5 running you
> have to inst
If you look the port source, you will see files/patch-setup.py in
which it disable md5 and such things like openssl. The only way to
have them back is :
1) modify this patch,
2) increment the release number in portfile
3) reindex all the port tree with portindex
4) finally reinstall the port after
Hi all,
yesterday I tried to install django on my macbook. Since I wanted to
have a more recent python interpreter I installed the one from
macports.
There's a pitfall, however. Because in order to get MD5 running you
have to install the package py25-hashlib as well! Otherwise you will
face the "
hey everyone,
should there be any reason for @staticmethod not to work in django model
classes?
or should I be using the non-decorator syntax?
( django dev server + python 2.5 )
- bram
--~--~-~--~~~---~--~~
You received this message because you are
Bram - Smartelectronix wrote:
> hey everyone,
>
>
> ( I hope you saw the question mark at the end of the subject ;-) )
>
> working in eclipse, it would be so wonderful to get auto completion and
> all those other goodies working. Auto completion works just fine for
> everything django (i.e. d
hey everyone,
( I hope you saw the question mark at the end of the subject ;-) )
working in eclipse, it would be so wonderful to get auto completion and
all those other goodies working. Auto completion works just fine for
everything django (i.e. django.*) but no matter what I try there's no
CTED]> wrote:
> Thanks,
>
> I'm getting the impression that MySQLdb is not available to Python 2.5,
> but if anyone is using this configuration, I would like to
> find out about the details. The OS in question is WinXP - Version 5.1.2600.
>
> Regards,
>
> CL
>
> B
Thanks,
I'm getting the impression that MySQLdb is not available to Python 2.5,
but if anyone is using this configuration, I would like to
find out about the details. The OS in question is WinXP - Version 5.1.2600.
Regards,
CL
Brett Parker wrote:
> On Wed, Jan 10, 2007 at 02:21:38
On 1/10/07, Carl Holm <[EMAIL PROTECTED]> wrote:
> After attempting to run Django with Python 2.5, I get the following
> after trying to connect: to dev server:
>
> 'Error loading MySQLdb module: No module named _mysql'
>
> Any furt
On Wed, Jan 10, 2007 at 02:21:38AM -0800, Carl Holm wrote:
>
> Hello,
>
> After attempting to run Django with Python 2.5, I get the following
> after trying to connect: to dev server:
>
> 'Error loading MySQLdb module: No module named _mysql'
>
>
Hello,
After attempting to run Django with Python 2.5, I get the following
after trying to connect: to dev server:
'Error loading MySQLdb module: No module named _mysql'
Any further info would be appreciated.
- CL
--~--~-~--~~~---~--~
On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
>
> Thanks but I don't have, and don't want an irc client, so I'll just
> struggle along and try not to ask stupid questions. My problem is that
> Python 2.5 and sqlite3 seems to be a buggy combination. (Is that tru
On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
>
> So 'DATABASE_NAME' should be the full name of a non-existant file. I
> had thought they wanted the path to where the file was located.
>
> !!Works fine now!!
>
> Two problems for Django with Python 2.5
So 'DATABASE_NAME' should be the full name of a non-existant file. I
had thought they wanted the path to where the file was located.
!!Works fine now!!
Two problems for Django with Python 2.5
bug 1)
ez_setup.py in Django .95 folder should have:
DEFAULT_VERSION = "0.
The the name to a file in a directory - SQLite databases are a single file,
and it won't be able to create one if a directory already exists with the
same name.
-joe
On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
>
>
> I tried to do:
> Python manage.py syncdb
> and got the error "No module name
I tried to do:
Python manage.py syncdb
and got the error "No module named pysqlite2". I edited the file
\Python25\Lib\site-packages\Django-0.95-py2.5.egg\django\db\backends\sqlite3\base.py
to read:
from sqlite3 import dbapi2 as Database
instead of
from pysqlite2 import dbapi2 as Database
and the e
>From Django Djumpstart I attemptd:
python manage.py syncdb
and got an error:
C:\Django\gtd>python manage.py syncdb
Traceback (most recent call last):
File "manage.py", line 11, in
execute_manager(settings)
File
"C:\Python25\lib\site-packages\django-0.95-py2.5.egg\django\core\manageme
nt.
Thanks but I don't have, and don't want an irc client, so I'll just
struggle along and try not to ask stupid questions. My problem is that
Python 2.5 and sqlite3 seems to be a buggy combination. (Is that true?)
Maybe sqlite3 hasn't really been integrated yet?
I have had to e
On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
> Jeremy Dunck wrote:
> > On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
...
> > Python's path (which is the list included in sys.path) is totally
> > separate from the window path.
> >
> So how do I put Django on this path?
>
> > You probably wan
Jeremy Dunck wrote:
> On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
> >
> > The command
> > C:>django-admin.py
> > does find it (tho it doesn't know what to do with it).
> >
> > It seems Python does not understand the path environment variable
> > or is there something I'm missing?
>
> Python'
On 12/14/06, kbochert <[EMAIL PROTECTED]> wrote:
>
> The command
> C:>django-admin.py
> does find it (tho it doesn't know what to do with it).
>
> It seems Python does not understand the path environment variable
> or is there something I'm missing?
Python's path (which is the list included in sy
I setup my path env var:
C:\Django>path
PATH=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program
Files\ATI Tech
nologies\ATI Control
Panel;C:\Apps\Eps12\Bin;C:\Python25;c:\Python25\Scripts;c:\
Django\django\bin
And I get:
C:\Django>python django-admin.py
python: can't open file 'django
I have problems to get mod-python for python 2.5 (win32). Does anybody
knows how to get this version.
Thanks!!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
On 9/20/06, John DeRosa <[EMAIL PROTECTED]> wrote:
[snip]
>
> It seems a little screwy for a file in a directory called "sqlite3" to
> do an import from "pysqlite2". But that's what it does.
>
What you need to realize is that "sqlite" refers to the database,
while "pysqlite" are the python bindi
On Thursday 21 September 2006 05:44, John DeRosa wrote:
> Oliver Andrich wrote:
> > Hi,
> >
> > I am running Django 0.95 . And so far I can't see any problems.
>
> How'd you do it?
>
> I'm on Windows XP. I installed Python 2.5 from python
tween setuptools 0.6 and python 2.5
So I just decided to checkout 0.7 from python svn sandbox.
It seems that they made 0.6 for python 2.5 and uploaded it to
the cheeseshop just after my "research" :)
regards,
Vladimir
Oliver Andrich wrote:
> On 9/20/06, Vladimir Cambur <[EM
Yesterday I posted a small patch to do this, please refer ticket #2772 :)
James Bennett wrote:
> On 9/20/06, Oliver Andrich <[EMAIL PROTECTED]> wrote:
>
>> For your own development environment this is more then okay in my
>> eyes. And I would even deploy with this small change. But this is
>>
On 9/20/06, James Bennett <[EMAIL PROTECTED]> wrote:
On 9/20/06, Oliver Andrich <[EMAIL PROTECTED]> wrote:> For your own development environment this is more then okay in my> eyes. And I would even deploy with this small change. But this is
> personal taste. :)Probably the best thing for us to do i
On 9/20/06, Oliver Andrich <[EMAIL PROTECTED]> wrote:
> For your own development environment this is more then okay in my
> eyes. And I would even deploy with this small change. But this is
> personal taste. :)
Probably the best thing for us to do in trunk is what we already do
with threading: tr
I've
> about reached my time limit on this experiment, so I'm going to revert
> to Python 2.4. :-(
pysqlite2 has been renamed to sqlite3 in Python 2.5, which is in my
eyes the clearer naming convention. Your problem can be easily fixed,
if you would like to do it.
- I checked out th
Oliver Andrich wrote:
> Hi,
>
> On 9/20/06, John DeRosa <[EMAIL PROTECTED]> wrote:
>> How'd you do it?
>>
>> I'm on Windows XP. I installed Python 2.5 from python.org without a
>> problem.
>>
>> But then I found that pysqlite Win
On 9/20/06, Vladimir Cambur <[EMAIL PROTECTED]> wrote:
> setuptools 0.6x does not work with python 2.5
> try developement version of setuptools from python svn sandbox
> http://svn.python.org/projects/sandbox/trunk/setuptools/
I downloaded the 0.6c2 ZIP File and installed it. No h
Hi,
On 9/20/06, John DeRosa <[EMAIL PROTECTED]> wrote:
> How'd you do it?
>
> I'm on Windows XP. I installed Python 2.5 from python.org without a
> problem.
>
> But then I found that pysqlite Windows binaries for Python 2.5 don't
> exist, and neither
Hi,
setuptools 0.6x does not work with python 2.5
try developement version of setuptools from python svn sandbox
http://svn.python.org/projects/sandbox/trunk/setuptools/
Vladimir
John DeRosa wrote:
> Oliver Andrich wrote:
>> Hi,
>>
>> I am running Django 0.95 . And s
Oliver Andrich wrote:
> Hi,
>
> I am running Django 0.95 . And so far I can't see any problems.
How'd you do it?
I'm on Windows XP. I installed Python 2.5 from python.org without a
problem.
But then I found that pysqlite Windows binaries for Python 2.5 don
On Wed, 20 Sep 2006 07:53, James Bennett wrote:
> On 9/19/06, Ramdas S <[EMAIL PROTECTED]> wrote:
> > Is anyone running Django dev version on Python 2.5? Will it work or are
> > there any issues?
>
> Python 2.5 doesn't break or remove anything, it just adds some n
On 20/09/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 9/19/06, Ramdas S <[EMAIL PROTECTED]> wrote:
> > Is anyone running Django dev version on Python 2.5? Will it work or are
> > there any issues?
>
> Python 2.5 doesn't break or remove anything
On 9/19/06, Ramdas S <[EMAIL PROTECTED]> wrote:
> Is anyone running Django dev version on Python 2.5? Will it work or are
> there any issues?
Python 2.5 doesn't break or remove anything, it just adds some new
features. So it should work just fine. Backwards compatibility o
1 - 100 of 102 matches
Mail list logo