Re: Goodbye, Malcolm
El martes, 19 de marzo de 2013 18:01:39 UTC+1, Jacob Kaplan-Moss escribió: > Hello fellow Djangonauts, > > We have difficult news: Malcolm Tredinnick has passed away. > > Malcolm was a long-time contributor to Django, a model community member, > a brilliant mind, and a friend. His contributions to Django — and to > many other open source projects — are nearly impossible to enumerate. > Many on the core Django team had their first patches reviewed by him; > his mentorship enriched us. His consideration, patience, and dedication > will always be an inspiration to us. > > To say we'll miss him is an understatement. > > Our thoughts are with Malcolm's friends, colleagues, and family at this > difficult time. > > This came as quite a shock, and we're still sorting out details. We'll > update our blog, > https://www.djangoproject.com/weblog/2013/mar/19/goodbye-malcolm/, > once we know the details of how you can express your condolences to > Malcolm's friends and family. > > — The Django Core Team > R.I.P. Thanks for all you've done for the community. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Handling millions of rows + large bulk processing (now 700+ mil rows)
I'm in :D El sábado, 30 de junio de 2012 17:10:27 UTC+2, Cal Leeming [Simplicity Media Ltd] escribió: > > Hi all, > > As some of you know, I did a live webcast last year (July 2011) on our LLG > project, which explained how we overcome some of the problems associated > with large data processing. > > After reviewing the video, I found that the sound quality was very > poor, the slides weren't very well structured, and some of the information > is now out of date (at the time it was 40mil rows, now we're dealing with > 700+mil rows). > > Therefore, I'm considering doing another live webcast (except this time > it'll be recorded+posted the next day, the stream will be available in > 1080p, it'll be far better structured, and will only last 50 minutes). > > The topics I'd like to cover are: > > * Bulk data processing where bulk_insert() is still not viable (we went > from 30 rows/sec to 8000 rows/sec on bulk data processing, whilst still > using the ORM - no raw sql here!!) > * Applying faux child/parent relationship when standard ORM is too > expensive (allows for ORM approach without the cost) > * Applying faux ORM read-only structure to legacy applications (allows ORM > usage on schemas that weren't properly designed, and cannot be changed - > for example, vendor software with no source code). > * New Relic is beautiful, but expensive. Hear more about our plans to make > an open source version. > * Appropriate use cases for IAAS vs colo with SSDs. > * Percona is amazing, some of the tips/tricks we've learned over. > > If you'd like to see this happen, please leave a reply in the thread - if > enough people want this, then we'll do public vote for the scheduled date. > > Cheers > > Cal > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/UFoiTSkA3zEJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: 1.4: Emails to BCC addresses not sent
El viernes, 6 de julio de 2012 15:58:50 UTC+2, Thomas escribió: > > ... > > If that fails as well, I guess a ticket is in order, but like I said >> "works for me" (in version 1.4). >> If that doesn't fail, then make sure cco is filled. >> > fwiw it works for me too in 1.4 using virtualenv. Thanks Melvyn for the > simple example. > > - Tom > Thank you for checking it out Tom. I wonder what may be the problem, this is puzzling me :-( -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/8DuuiqzebFYJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: 1.4: Emails to BCC addresses not sent
El viernes, 6 de julio de 2012 12:59:23 UTC+2, Melvyn Sopacua escribió: > > On 6-7-2012 11:36, Javi Romero wrote: > > Does this sound like I should open a new ticket on the bugtracker or > does > > this work right for anyone else? > > It definitely works for me, when I do some testing with the EmailMessage > object. You should reduce your testing to just sending a simple message > with the EmailMessage class, like: > from django.core.mail import EmailMessage > > msg = EmailMessage( > subject='test', > to=['m...@example.org'], > bcc=['nowh...@example.org'], > body='test' > ) > msg.send() > > If that fails as well, I guess a ticket is in order, but like I said > "works for me" (in version 1.4). > If that doesn't fail, then make sure cco is filled. > -- > Melvyn Sopacua > > Well I just tested this again on a clean project, with only that code and a HttpResponse as return value on a single view, on both Django 1.3 and 1.4, on my usual development machine (Archlinux) and on a fresh VirtualBox install of Kubuntu 12.04 The only thing that I can think of that all the setups also have in common is python2.7 and the use of virtualenv, but even if I install django as a system package, I get the same output: 1.4 $ python2 manage.py runserver Validating models... 0 errors found Django version 1.4, using settings 'bcc.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: test From: webmaster@localhost To: m...@example.org Date: Fri, 06 Jul 2012 12:01:03 - Message-ID: <20120706120103.4768.10823@k-VirtualBox> test --- [06/Jul/2012 07:01:03] "GET / HTTP/1.1" 200 10 1.3 $ python2 manage.py runserver Validating models... 0 errors found Django version 1.3.1, using settings 'bcc13.settings' Development server is running at http://127.0.0.1:8000/ Quit the server with CONTROL-C. Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: test From: webmaster@localhost To: m...@example.org Date: Fri, 06 Jul 2012 12:12:08 - Message-ID: <20120706121208.5531.28602@k-VirtualBox> test --- [06/Jul/2012 07:12:08] "GET / HTTP/1.1" 200 10 Thank you very much for your cooperation, I'll open a bug and try to help finding out whats wrong :-). -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/HFYo_47q7igJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: 1.4: Emails to BCC addresses not sent
As usual, the webfaction support team is impresive in its support. Here's the extract from the mail log after sending the contact form. As it can be seen, there is no trace of bcc addresses. Also, the addresses to be bcc'ed are not the same that the one on the "To" field. Jul 5 11:15:56 mail6 postfix/smtpd[24001]: 1A216210E8AE: client=web317.webfaction.com[85.17.23.88], sasl_method=CRAM-MD5, sasl_username=batl...@smtp.webfaction.com Jul 5 11:15:56 mail6 postfix/cleanup[23507]: 1A216210E8AE: message-id=<20120705161555.19081.91...@web317.webfaction.com> Jul 5 11:15:56 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 11:16:26 mail6 postfix/smtp[23745]: 1A216210E8AE: to=, relay=none, delay=30, delays=0.39/0/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 11:46:05 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 11:47:00 mail6 postfix/smtp[25697]: 1A216210E8AE: to=, relay=none, delay=1864, delays=1809/25/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 12:19:22 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 12:20:02 mail6 postfix/smtp[27946]: 1A216210E8AE: to=, relay=none, delay=3847, delays=3806/10/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 13:26:00 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 13:27:00 mail6 postfix/smtp[4785]: 1A216210E8AE: to=, relay=none, delay=7864, delays=7804/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 14:49:20 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 14:50:08 mail6 postfix/smtp[16526]: 1A216210E8AE: to=, relay=none, delay=12853, delays=12804/18/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 16:12:40 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 16:13:40 mail6 postfix/smtp[23562]: 1A216210E8AE: to=, relay=none, delay=17864, delays=17804/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 17:36:00 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 17:37:00 mail6 postfix/smtp[2988]: 1A216210E8AE: to=, relay=none, delay=22864, delays=22804/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 18:59:20 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 19:00:11 mail6 postfix/smtp[11827]: 1A216210E8AE: to=, relay=none, delay=27856, delays=27804/30/21/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection refused) Jul 5 20:22:42 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 20:23:41 mail6 postfix/smtp[18908]: 1A216210E8AE: to=, relay=none, delay=32865, delays=32806/28/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 21:46:00 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 21:47:00 mail6 postfix/smtp[28019]: 1A216210E8AE: to=, relay=none, delay=37864, delays=37804/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 5 23:09:20 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 5 23:10:02 mail6 postfix/smtp[6562]: 1A216210E8AE: to=, relay=none, delay=42846, delays=42805/32/9.3/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection refused) Jul 6 00:32:40 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 6 00:33:40 mail6 postfix/smtp[15683]: 1A216210E8AE: to=, relay=none, delay=47865, delays=47805/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 6 01:56:00 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 6 01:57:00 mail6 postfix/smtp[24233]: 1A216210E8AE: to=, relay=none, delay=52864, delays=52804/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Jul 6 03:19:20 mail6 postfix/qmgr[3022]: 1A216210E8AE: from=, size=1416, nrcpt=1 (queue active) Jul 6 03:20:21 mail6 postfix/smtp[315]: 1A216210E8AE: to=, relay=none, delay=57865, delays=57805/30/30/0, dsn=4.4.1, status=deferred (connect to example.org[192.0.43.10]: Connection timed out) Does this sound like I should open a new ticket on the bugtracker or does this work right for anyone else? El viernes, 6 de julio de 2012 10:35:09 UTC+2, Javi Romero escribió: > > > > El viernes, 6 de julio de 2012 02:18:43 UTC+2, Melvyn Sopacua escribió: >
Re: 1.4: Emails to BCC addresses not sent
El viernes, 6 de julio de 2012 02:18:43 UTC+2, Melvyn Sopacua escribió: > > On 5-7-2012 19:44, Javi Romero wrote: > > Hi list, I'm new around though I've been developing Django sites since > the > > early 1.0 releases > > > > I've been looking around for problems regarding email sending to BCC > > addresses but can't find anything that explains what I'm seeing. > > You've included a lot of information, except the mail log on the MTA > that django connects to and that's the crucial thing. You'll need to > verify if the bcc addresses are showing up to determine the guilty party. > > Also, if you bcc something to a recipient already in the recipient list, > it is not guaranteed they receive two copies and even more likely that > they don't, so use addresses you know are good but not in the list > already. > -- > Melvyn Sopacua > > Hello Melvyn, thank you for your input. I've requested the log to the production server's support team to provide further context. In the meanwhile, is there any other relevant data I can provide from my development machine? I'll be more than glad to shed some light on this. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/xBB5iDm9zIwJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
1.4: Emails to BCC addresses not sent
Hi list, I'm new around though I've been developing Django sites since the early 1.0 releases I've been looking around for problems regarding email sending to BCC addresses but can't find anything that explains what I'm seeing. I have a ModelForm that renders a pretty simple contact form, and on POST the instance of the model gets saved. In that method, I've implemented a simple email sending step and then it continues normally. Code is on bottom. I've tried this with both EmailMultiAlternatives and EmailMessage, and with the IMAP and Console email backends, and on my local machine and on remote servers (webfaction). The emails always go to the address in the "To" field, but the "BCC" ones, no matter if it's only one and the same than "To" or if they are a few different emails never receive anything. On both the IMAP and the Console backends I get output similar to this: -- MESSAGE FOLLOWS -- Content-Type: multipart/alternative; boundary="===1548201696055964499==" MIME-Version: 1.0 Subject: Nuevo mensaje de test12 recibido en example.com From: direcc...@example.com To: tes...@test.es Date: Thu, 05 Jul 2012 10:06:59 - Message-ID: <20120705100659.9464.36431@i5-750> X-Peer: 127.0.0.1 --===1548201696055964499== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Hola test12, acabamos de recibir tu mensaje y nos pondremos en contacto contigo lo antes posible. ab7 Cosmética --===1548201696055964499== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Hola test12, acabamos de recibir tu mensaje y nos pondremos en contacto contigo lo antes posible. http://example.com/media/configuracion/ab7_logo.png"; alt="ab7 Cosmética" />ab7 Cosmética --===1548201696055964499==-- END MESSAGE Notice that, if you look at the headers, there is no sight of "BCC" fields or addresses. I've looked at the variables that contains the BCC addresses and they look right, something like [u'f...@mail.com', u'b...@mail.com']. Also, if I check msg.recipients() I get a full list of every addresses, both To and BCC, what anyone would expect. I've changed the bcc parameter to cc on the construction of the message instance and it appears on the headers of the message and gets delivered to the emails. So, any idea of what may be happening? I'm pretty lost right now and don't know what else try to fix this :-/ Original code follows: # -*- coding: utf-8 -*- ''' Javier Romero Desarrollado por Barrabarra web: http://barrabarra.es Fecha: 2012 ''' from django.conf import settings from django.contrib.sites.models import Site from django.contrib.sites.managers import CurrentSiteManager from django.core.mail import EmailMessage, EmailMultiAlternatives from django.db import models from django.db.models.signals import post_save from django.template.loader import render_to_string from django.utils.translation import ugettext_lazy as _ from catalog.models import Product from configuracion.models import Configuracion from sorl.thumbnail import ImageField class ContactConfig(models.Model): """ Contact main configuration, contains title and description for both form and sent pages """ contacto_titulo = models.CharField(verbose_name=_(u'Título de la página de contacto'), max_length=120) contacto_texto = models.TextField(verbose_name=_(u'Contenido'), blank=True,) contacto_analytics = models.TextField(verbose_name=_(u'Analytics de la página de contacto'), blank=True,) contacto_imagen = ImageField(_(u'Imagen de la página de contacto'), blank=True, upload_to='contacto') exito_titulo= models.CharField(verbose_name=_(u'Título de la página de formulario enviado'), max_length=120) exito_texto = models.TextField(verbose_name=_(u'Contenido'), blank=True,) exito_analytics = models.TextField(verbose_name=_(u'Analytics de la página de formulario enviado'), blank=True,) exito_imagen= ImageField(_(u'Imagen de la página de formulario enviado'), blank=True, upload_to='contacto') analytics_contacto = models.TextField(verbose_name=_(u'Analytics del botón de formulario de contacto completo'), blank=True,) analytics_contactame = models.TextField(verbose_name=_(u'Analytics del botón de formulario de contacto rápido'), blank=True,) creado_el = models.DateTimeField(_(u'Creado el'), editable=False, auto_now_add=True) actualizado_el = models.DateTimeField(_(u'Actualizado el'), editable=False, auto_now=True) class Meta: verbose_name = _(u'Configuración de contacto') verbose_name_plural = _(u'Configuración de contacto') class NotificationEmail(models.Model): """ Email addresses to be notified when contact forms are sent, editable on admin instead of putting them on the settings file """
