> If you managed to get it compiling and working, well done, a lot of people > already stop at that point.
In contrast with the other compilings, I found lighttpd is easy (except that the info I first read not talk about the switch to enable fastcgi) > Was this only because of the missing/non-working of the MSSQL database > connector? No. Was the necesary setup to get python working. First, found a way to setup it under IIS was impossible by the lack of fastcgi support (CGI can be worked, but that is a bad idea anyway)... only this day somebody post in this list about support of it for IIS. Next, the need of a rewriter (IIS not have one installed)... I get a .NET based but then is necesary to install ISAPI filters and other things and the only way to get .fcgi to work involve the registry. A lot of thing that not like a host company in a shared environment. > 2 Python versions? Sounds like strange dependencies between system > needed Python version (2.3 perhaps?) and newer Python 2.4. A bit silly > in my personal opinion, but ok. You could also try to use setuptools' > easy_install to install these packages. easy_install mysqldb will > fetch from the Python CheeseShop and build and install it for you (it > should get placed in your active Python install, probably something > like /usr/local/lib/python2.4/site-packages/). easy_install not work reliably. In fact, I only get to work for python-only components with not dependencies in anything about the OS. > Personally I'd dare to say MSSQL and PostgreSQL share more than MSSQL and > MySQL. Maybe. I don't know, and aftet this experience I learn to be more carefull about the things I don't know... > I am of the mindset that if we can support it we should just try to > support it. I think I still have the SQL Server Express 2005 installed > on my workstation, I should try and see what if needed to get this > working as it should. I work with SQL 2000 mainly but I have SQL 2005 in the desk... But taking in account the large poll of SQL 2000 installation I think is necesary support both (not that hard anyway, is only a diferent connection strings and minimal diferences, that its, if nothing fancy is added. From the point of view of a ORM, any database is almost equal, because not SP, no VIEWS and that stuff is not -normally- in the mix) > But merely because people will want to use it. Glad to know. I have my eyes checking the progress each week. When I see some progress on this (or found time to hack on it ;) I dream about django under IronPython and I'm thinking seriously about build a product for my company based in django, and full Windows support is a must. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
