Just for the record, to close this off - the problem was solved when I
finally configured Django to send email via my *ISP*. Apparently
Django was doing some unnecessary formatting, whether the output went
to file, console, or even *smtp*, going to a local smtp server: python
-m smtpd -n -c Debuggi
(sigh) Naturally as soon as I hit the [send] button, another question
comes up :) I switched to my VPS, and was thinking about where to
create a project, when I was wondering:
How do people generally organize their virtualenv directories, and
Django projects?
I'm on as root on my machine, and und
Thanks all, great answers. Sounds like virtualenv is better than I
thought. And Shawn cleared up one of the misconceptions I had, I
didn't realize it was possible to alt-install multiple versions of
Python - I was trying to install 2.6 *under* virtualenv, which is not
how it works. :)
Still not fi
I'd like to know what kind of experience people have had, in using
virtualenv (to run a particular version of Python on a VPS) with
Django, and related packages? Not *just* Django (and Python), I'm
fairly sure that will work, but all the other bits and pieces that
tend to be required, like mod_wsgi
> Actually, it doesn't. It only has utf-8. The first nine lines of your pasted
output are the actual email headers.
Okay, that makes more sense. That particular experiment I was using a
MIMEObject's to_string() function. Although I had passed in plain text
to the object, clearly it put its own hea
> What are you *actually* doing to send this email?
This is the basic version - the one with two headers, I was
experimenting with a MIMEText object:
from django.core.mail import send_mail
def page_worked(request):
the_text = u'this is a test of a really long line that has more
words that co
Actually, upon looking more at the output, it has *both* "utf-8" and
"us-ascii" as the charset. I'm not sure if this is the result of code
changes I've made, or I just missed it the first time around - but my
Django email output now looks like this:
-- MESSAGE FOLLOWS --
Content-Ty
> The only encoding that isn;t going to wrap is charset="us-ascii"
Actually, looking at the resulting file, it *does* say it's
charset="us-ascii".
> An email client would read "=\r\n" as a soft line break, and remove it
> when displaying the message.
I tried cutting/pasting the text, and sendin
I'm using the filebased email backend for testing (although the
console version had the same problem). When I send email, either via
function or template, lines that are too long, are broken, with an
'=' sign at the end. For instance:
this is a test of a really long line that has more words th
Arg - I meant 127.0.0.1:8000
Is there a way to edit messages that I dont see here? :)
John C>
On May 7, 10:17 am, John Crawford wrote:
> I'm not sure why your address is all zeros, did you give a specific
> host number parameter to runserver?
>
> Generally 127.0.0.
I'm not sure why your address is all zeros, did you give a specific
host number parameter to runserver?
Generally 127.0.0.0:8000 would be your localhost, and that is the
default for runserver. Use that instead (or don't give it any
parameters), see what happens.
John C>
--~--~-~--~~-
Okay, I'm not sure why the OP code didn't work - it seems like going
to the URL 'lists/show', with the updated list, would work. So my
*guess* is that since it's a page the browser already saw and cached,
that the page just isn't getting refreshed. In other words, if he hit
the browser-refresh but
> Django doesn't ship anything for XML serialization or deserialization,
> but Python does.
Actually, Django does provide that capability, at least in 1.0/1.1:
http://docs.djangoproject.com/en/dev/topics/serialization/#topics-serialization
Supported formats include XML, JSON (via simplejson),
be
funny :)
Sorry again.
John C>
Jacob Kaplan-Moss wrote:
> On Sun, Mar 15, 2009 at 5:40 PM, John Crawford wrote:
> > Anyone? Anyone? Bueller?
>
> That's rude.
>
> Please don't take the amazing work of the volunteers on this board for
> granted. Nobody here
Anyone? Anyone? Bueller?
John Crawford wrote:
> Hello, I have been looking for Django-based forum-building software,
> and so far, the two best candidates are Snap and SCT. Does anyone have
> any experience with either, and willing to comment on them? Or are
> there other apps t
Hello, I have been looking for Django-based forum-building software,
and so far, the two best candidates are Snap and SCT. Does anyone have
any experience with either, and willing to comment on them? Or are
there other apps that might be better than those? Thanks.
John C>
--~--~-~--~
16 matches
Mail list logo
