On Jan 5, 2:24 pm, "Karen Tracey" <kmtra...@gmail.com> wrote:
> On Mon, Jan 5, 2009 at 6:49 AM, Filipe <fcorr...@gmail.com> wrote:
> Assuming you are not the person who called himself Friendless over on
> django-users recently, you are the 2nd person to report a pr
ifferently? Is there an option I
can use to reset the password?
Thank you in advance!
Cheers,
Filipe Correia
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
pose
> a security risk, not because of display problems. The solution to
> "unusual characters" is Unicode :)
so, if I have all template files utf-8 encoded and only pass them
unicode strings, the browser will always display "unusua
ot; (single quote) to ''
Wouldn't it be nice if it replaced a wider range of characters? not
sure how useful it would be, but i think some unusual characters may
not be displayed correctly if not escaped.
There are a couple more escapable characters than the ones
Do you know if something equivalent to the "DTM Migration Kit" you
mentioned exists as open software? Using a commercial product is not
very practical in my case, because the clients would have to agree on
buying it, which I belive is not likely.
res in this project of mine, but the data I
need is already "packaged" in a MSSqlServer database, so my choice is
bit limited for now.
regards,
Filipe
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django deve
ADO, but I
think that's irrelevant in this case. any solution found for pymssql
should also work with other providers, and vice-versa.
http://groups.google.com/group/django-developers/browse_frm/thread/6fa803c0fdcb82f3/3afb2c92f67d0511
hope this helps,
Filipe
Jacob Kaplan-Moss wrote:
> On Jul 5, 2006, at 9:05 AM, Filipe wrote:
> > and the first changes towards that will start appearing in python 2.5:
> > http://www.python.org/dev/peps/pep-0332/
>
> Er, no -- that PEP was actually rejected. My impression is that the
> str/u
Andrey Golovizin wrote:
> Jacob Kaplan-Moss wrote:
> > "... with too many backwards-incompatible changes ..." -- as Hugo
> > points out, this will break a lot of existing code.
> Well, some day Django will have to switch to unicode anyway (even Python-3000
> is going to use unicode strings
