On Fri, Aug 31, Anderson Santos wrote:
>
> Ahhh, finally!
Fine!
>
> Thank you very much, it worked now =D
> I didn't know about the __unicode__ trick
Well, the unicode documentation is dense to read, so one shouldn't rush
through it. But it contains also this trick:
http://www.djangoprojec
Ahhh, finally!
Thank you very much, it worked now =D
I didn't know about the __unicode__ trick
And I am not sure if it is it that you want to know, but I still not
using the encoding header on the top of the files. I thought it was
more to the enconding chars of the file and not an advanced set
On Fri, Aug 31, Anderson Santos wrote:
>
> Here the code:
>
>
> class Download(models.Model):
> """ Disponibilização de arquivos para download """
>
> descricao =
> models.CharField(verbose_name='Descrição',maxlength=250)
> data_do_arquivo = models.DateField()
> caminho_do_arq
Here the code:
class Download(models.Model):
""" Disponibilização de arquivos para download """
descricao =
models.CharField(verbose_name='Descrição',maxlength=250)
data_do_arquivo = models.DateField()
caminho_do_arquivo = models.CharField(maxlength=400)
atualizar_versao_com
On Thu, Aug 30, Anderson Santos wrote:
>
> I am still having this issue.
> I have in my settings DEFAULT_CHARSET = "utf-8", and I created a new
> database with UTF-8 encoding (using PGAdmin).
> So I go to admin page, click on my model and then the "add" button, I
> include a special char (á, ç,
18:30, Anderson Santos <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> I am migrating a stable lighttpd+fcgi django app to apache+mod_python
> and I am dealing with a strange encoding behavior. Here what I did:
>
> With a plain migration from the working app to the new mod_python o
Hello,
I am migrating a stable lighttpd+fcgi django app to apache+mod_python
and I am dealing with a strange encoding behavior. Here what I did:
With a plain migration from the working app to the new mod_python one
I got a lot of LATIN1 codec errors that never occured on the last
architecture
7 matches
Mail list logo
