Re: py2neo - how to get a node

[Ramiro Morales]

On Jun 12, 2015 7:28 PM, "Shekar Tippur"  wrote:
>
> Hello,
>
> I am trying to use py2neo (http://py2neo.org/2.0/ext/ogm.html).
> I am having trouble looking up a node.

Wouldn't this post be more appropriate for the py2neo users mailing list or
similar?

Just in case, you posted your message to the Django users mailing list.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAO7PdF__RwnX8qvkgvt1RYsV8_i2UBRjSdW-qC5zv29oZ1OTuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

py2neo - how to get a node

[Shekar Tippur]

Hello,

I am trying to use py2neo (http://py2neo.org/2.0/ext/ogm.html).
I am having trouble looking up a node.

Here is my code:

lookupname="Shekar"

Shekar=store.load_indexed('Person','Name','Shekar',Person)


This returns a list. I want the complete object so that I can use in a 
relationship


Like 


store.relate(Shekar, "LIKES", Mango)


When I try this, I get an error:


'list' object has no attribute '__dict__'


- Shekar

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4c5d69b7-3101-482a-8da0-83c75acd6c1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: HTTPS on docs.djangoproject.com

[Davor Lučić]

Cool, thank you

On 12 June 2015 at 21:13, Markus Holtermann 
wrote:

> Hey,
>
> Not on djangoproject.com but you can use http://django.readthedocs.org/
>
> /Markus
>
> On June 12, 2015 8:32:09 PM GMT+02:00, "Davor Lučić" 
> wrote:
> >Hello,
> >
> >Is it possible to request documentation on docs.djangoproject.com
> >without
> >HTTPS?
> >
> >I work for corporation that either blocks or uses MITM certs for HTTPS
> >and
> >I am unable to access Django documentation since its forcing me to use
> >HTTPS even when i request HTTP.
> >
> >Thank you,
> >Davor
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/4CE6801E-9735-41EE-9F3D-6195F7CBB97F%40markusholtermann.eu
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAKB_9CLuc%3D9HiGjudsCha2VVac-myFmyLm4uMvE%3DiLkQgR4r6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: HTTPS on docs.djangoproject.com

[Markus Holtermann]

Hey,

Not on djangoproject.com but you can use http://django.readthedocs.org/

/Markus

On June 12, 2015 8:32:09 PM GMT+02:00, "Davor Lučić"  wrote:
>Hello,
>
>Is it possible to request documentation on docs.djangoproject.com
>without
>HTTPS?
>
>I work for corporation that either blocks or uses MITM certs for HTTPS
>and
>I am unable to access Django documentation since its forcing me to use
>HTTPS even when i request HTTP.
>
>Thank you,
>Davor

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4CE6801E-9735-41EE-9F3D-6195F7CBB97F%40markusholtermann.eu.
For more options, visit https://groups.google.com/d/optout.

Django/djcelery 1.8.2 AppRegistryNotReady: Translation infrastructure cannot be initialized

[Manas Hardas]

Sorry if this is not an appropriate place for a django/djcelery related 
error.

I am getting the following error:

File 
"/Library/Python/2.7/site-packages/Django-1.8.2-py2.7.egg/django/utils/translation/trans_real.py",
 line 164, in _add_installed_apps_translations"The translation infrastructure 
cannot be initialized before the "
django.core.exceptions.AppRegistryNotReady: The translation infrastructure 
cannot be initialized before the apps registry is ready. Check that you don't 
make non-lazy gettext calls at import time.

I have a project which is not really a django app but a celery app. 
Therefore, I have not created a wsgi.py or models.py or any of the typical 
files created by django-admin when a project or app is started.

I only want to use djcelery to be able to create periodic tasks using the 
djcelery.schedules.DatabaseScheduler like specified here Add, modify, 
remove celery.schedules at run time 

 and 
here How to dynamically add / remove periodic tasks to Celery (celerybeat) 


The solution to the problem as given here (AppRegistryNotReady, translation 
bug when deploying with uWSGI ) 
requires me to make changes to vassal.ini file. There is no vassal.ini file 
in my implementation.

I will briefly describe my proj -

proj
  apps.py
  tasks.py
  celeryconfig.py
  runproj.py
- apps.pyfrom celery import Celery
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'celeryconfig')
myapp = Celery('myapp')
myapp.config_from_object('celeryconfig')if __name__ == '__main__'
myapp.worker_main('--loglevel=DEBUG', '-B', '-S', 
'djcelery.schedules.DatabaseScheduler')
- tasks.pyfrom apps import my...@myapp.task(name='proj.msg_printer')def 
msg_printer(msg):
print msg
- runproj.pyfrom djcelery.models import PeriodicTask, IntervalSchedule
intSch = IntervalSchedule(period='seconds', every=30)
periodic_task = PeriodicTask(
  name = '30-sec-msg-printer',
  task = 'proj.tasks.msg_printer',
  interval = intSch,
  args=json.dump(['such-wow']),
 )
periodic_task.save()
- celeryconfig.py
CELERY_ACCEPT_CONTENT = ['pickle', 'json']
BROKER_URL = 'amqp://guest@localhost'
CELERY_IMPORTS = ('proj.tasks')
CELERY_QUEUES = [Queue('default', Exchange('default', type='direct'), 
routing_key='default')]
#DJANGO SETTINGS
INSTALLED_APPS = 
('django.contrib.admin','django.contrib.auth','django.contrib.contenttypes','django.contrib.sessions','django.contrib.messages','django.contrib.staticfiles','djcelery',)

DATABASES = {'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': os.path.join('/home', 'test.db'),
}}

Before I run the workers I created the required tables using the django-admin 
migrate command. I can see the relevant tables to store interval schedules 
and periodic tasks in the /home/test.db database.

First I run the workers - $python apps.py Then I save a schedule to the 
database to be executed repeatedly by celerybeat daemon - $python runproj.py

Any thoughts? Thank you.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ac452147-6798-46f3-a2d2-2b0177011a82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

HTTPS on docs.djangoproject.com

[Davor Lučić]

Hello,

Is it possible to request documentation on docs.djangoproject.com without
HTTPS?

I work for corporation that either blocks or uses MITM certs for HTTPS and
I am unable to access Django documentation since its forcing me to use
HTTPS even when i request HTTP.

Thank you,
Davor

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAKB_9CLJtnxFCzhrWt1rbErhR0nW6J5HqsYGnvo3FaTk5kq_0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Squashed migration

[Carl Meyer]

Hi Cherie,

On 06/12/2015 06:32 AM, Cherie Pun wrote:
> Thanks for your replies! I am still on Django 1.7 but we are hoping to
> upgrade to 1.8 soon. I manage to use the squashed migrations when
> creating the test database now,

Do you know why it didn't work initially? That'd be useful to know, in
case it's something that might trip up other users, too.

> but there's syntax error in the
> automatically generated squash migration. The error occurs on the line
> on which it reference the user-defined functions in other migrations. It
> seems fine when it ran the first methods though.

That sounds like a probably-fixable bug (though it may already be fixed
in 1.8 and/or master). If you're able to reproduce the bug on master,
please do file a ticket for it.

Carl

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/557AFE4C.7060403%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: Squashed migration

[Carl Meyer]

On 06/12/2015 06:32 AM, aRkadeFR wrote:
> You need to delete your old migrations so it uses only the squashed
> one after.

No, the squashed migration should be used in place of the old ones for
any new database, even if the old ones are still present. This is the
point of the squashmigrations feature; that you can keep the old ones
around (which is necessary for any deployments that may not yet have
applied all of them) while still gaining the benefit of the new squashed
migration for new deployments (and tests).

I know this works, because I just did it recently myself. It sounds like
Cherie was able to get it working too, though we didn't get any
clarification on why it didn't seem to work originally.

> In the documentation:
> "This enables you to squash and not mess up systems currently in
> production that aren’t fully up-to-date yet. The recommended process is
> to squash, keeping the old files, commit and release, wait until all
> systems are upgraded with the new release (or if you’re a third-party
> project, just ensure your users upgrade releases in order without
> skipping any), and then remove the old files, commit and do a second
> release."

That's right. The length of time you need to wait before removing can
vary widely. For a third-party app, it may be a full release cycle or
two (as long as you can tell your users to upgrade version-by-version).
For a project with only a few deployments, all under your control, it
may be the same day. But regardless, the squashed migration will still
be used in tests immediately, before you remove the old migrations.

Carl

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/557AFDF3.1090900%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

What are some good 3rd party django apps to build a user dashboard and folder management (similar to a Google drive account)

[Shanu Kumar]

Hi,

I have been trying to find an app which helps build a user-specific 
file/folder management system.

An example for this could be an app that is exactly similar to your google 
drive account. The operations performed by the app could be a subset of 
what a google drive account does:
1. Organization of folders into Shared with me, Starred, Recent.
2. Showing details and activity associated with a specific folder
3. Displaying the permission level that each user has with a folder etc.

I tried searching for this but could not find an app that could meet these 
specifics.

Thanks.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ad344f05-d5a6-4828-8874-fab9f64fc89d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 想用中文说清楚：我在远程工作机服务器上建立了django框架，想启动web server ，启动成功，但是无法打开127.0.0.1:8000 ，中间端口转接该怎么做

[David Wong]

127.0.0.1只能本机访问，其他网络终端要访问就得使用更大范围的网络段。如果两台机器同在一个局域网，那可以用局域网IP，如192.168.1.11这样的，如果不在局域网内那么就得用公网IP。前提是服务器上的django服务端口得绑定在你所访问的ip上

发自我的 iPhone

> 在 2015年6月11日，22:45，Sergiy Khohlov  写道：
> 
>  127.0.0.1  is always your local PC. 
>  you should use another one interface for accessing from remote host. 
>  if  your local PC has IP 192.168.0.10 
>   right syntax is django-admin.py runserver 192.168.0.10:8000
> 
> Many thanks,
> 
> Serge
> 
> 
> +380 636150445
> skype: skhohlov
> 
>> On Thu, Jun 11, 2015 at 5:26 PM, Neto  wrote:
>> 通过远程计算机，您无法打开地址？如果是这样，你应该用你的电脑的IP要访问。
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/029d94b6-7967-4921-ba3e-16c8d3fe3a01%40googlegroups.com.
>> 
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CADTRxJM_jDHYqbRJ_j-qsEODfDpGpdEsHrUYRjSsVY1UMJsxsg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/32BC3037-ACBF-4B3A-9368-3FB9279A6379%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Squashed migration

[aRkadeFR]

Hey,

You need to delete your old migrations so it uses only the squashed
one after.

In the documentation:
"This enables you to squash and not mess up systems currently in 
production that aren’t fully up-to-date yet. The recommended process is 
to squash, keeping the old files, commit and release, wait until all 
systems are upgraded with the new release (or if you’re a third-party 
project, just ensure your users upgrade releases in order without 
skipping any), and then remove the old files, commit and do a second 
release."


https://docs.djangoproject.com/en/1.8/topics/migrations/#squashing-migrations

On 06/12/2015 11:38 AM, Cherie Pun wrote:

Hi,

I have trying to experiment with squashmigration to see if it will 
make it faster to build the database when running tests. So I have 
squashed the migrations following the instructions on the Django 
website. However when I run the tests, it still uses the original 
migrations. I thought Django automatically uses the squashed one over 
the separated ones. Is there some settings that I have to configure? 
Also, it says that no optimisation was available even though there are 
a few AddField which should in theory be combined into AddModel.


Any help or suggestions will be much appreciated, thanks!

Cherie
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9288958d-0214-4cd2-9b51-dd173a8e83ae%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
aRkadeFR

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/557AD178.9090707%40arkade.info.
For more options, visit https://groups.google.com/d/optout.

Re: Squashed migration

[Cherie Pun]

Hi,

Thanks for your replies! I am still on Django 1.7 but we are hoping to 
upgrade to 1.8 soon. I manage to use the squashed migrations when creating 
the test database now, but there's syntax error in the automatically 
generated squash migration. The error occurs on the line on which it 
reference the user-defined functions in other migrations. It seems fine 
when it ran the first methods though.

Cheers, 
Cherie

On Friday, June 12, 2015 at 12:17:38 PM UTC+1, Filipe Ximenes wrote:
>
> Hi Cherie, maybe you can run your tests without the migrations. This 
> django app may solve your problem: 
> https://github.com/henriquebastos/django-test-without-migrations/
>
> On Fri, Jun 12, 2015 at 6:38 AM, Cherie Pun  > wrote:
>
>> Hi,
>>
>> I have trying to experiment with squashmigration to see if it will make 
>> it faster to build the database when running tests. So I have squashed the 
>> migrations following the instructions on the Django website. However when I 
>> run the tests, it still uses the original migrations. I thought Django 
>> automatically uses the squashed one over the separated ones. Is there some 
>> settings that I have to configure? Also, it says that no optimisation was 
>> available even though there are a few AddField which should in theory be 
>> combined into AddModel.
>>
>> Any help or suggestions will be much appreciated, thanks!
>>
>> Cherie
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/9288958d-0214-4cd2-9b51-dd173a8e83ae%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>   
>
> *Filipe Ximenes*+55 (81) 8245-9204
>
> *Vinta Software Studio*http://www.vinta.com.br
>  

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d997ffc2-b35e-4587-a278-cb2176f2cff5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Squashed migration

[Filipe Ximenes]

Hi Cherie, maybe you can run your tests without the migrations. This django
app may solve your problem:
https://github.com/henriquebastos/django-test-without-migrations/

On Fri, Jun 12, 2015 at 6:38 AM, Cherie Pun  wrote:

> Hi,
>
> I have trying to experiment with squashmigration to see if it will make it
> faster to build the database when running tests. So I have squashed the
> migrations following the instructions on the Django website. However when I
> run the tests, it still uses the original migrations. I thought Django
> automatically uses the squashed one over the separated ones. Is there some
> settings that I have to configure? Also, it says that no optimisation was
> available even though there are a few AddField which should in theory be
> combined into AddModel.
>
> Any help or suggestions will be much appreciated, thanks!
>
> Cherie
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/9288958d-0214-4cd2-9b51-dd173a8e83ae%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 


*Filipe Ximenes*+55 (81) 8245-9204

*Vinta Software Studio*http://www.vinta.com.br

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAA-QWB2LMVvigsNXfo3bRfidTAd%3DmgctQ9Trmm4tO%2BqMGfdi%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Squashed migration

[Erik Cederstrand]

> Den 12/06/2015 kl. 11.38 skrev Cherie Pun  >:
> 
> Hi,
> 
> I have trying to experiment with squashmigration to see if it will make it 
> faster to build the database when running tests. So I have squashed the 
> migrations following the instructions on the Django website. However when I 
> run the tests, it still uses the original migrations. I thought Django 
> automatically uses the squashed one over the separated ones. Is there some 
> settings that I have to configure? Also, it says that no optimisation was 
> available even though there are a few AddField which should in theory be 
> combined into AddModel.

squashmigrations has limits to what it can do. You are free to edit the 
migration by hand if you can spot any more optimizations, and file a bug report 
if you spot something that the squasher should reasonably detect.

Have you seen the new "manage.py test --keepdb" in Django 1.8? I have a 
complicated project with lots of apps and use it daily to speed up testing. 
https://docs.djangoproject.com/en/1.8/ref/django-admin/#test-app-or-test-identifier
 


Erik

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5968C3C9-1515-4B61-9E9C-964EC60B030E%40cederstrand.dk.
For more options, visit https://groups.google.com/d/optout.

Re: Django users Group admin

[Russell Keith-Magee]

Hi Eike,

I'm an admin; feel free to mail me any list admin requests.

Yours,
Russ Magee %-)

On Friday, June 12, 2015, Eike Post  wrote:

> Hello Django users,
> does anybody of you know how to get in touch with the Django user group
> admin?
> I tried via contact admin and tried emailing to these emails:
> django-users+ad...@googlegroups.com
> 
> django-users+ow...@googlegroups.com
> .
> But nothing worked so far.
> Any suggestions?
>
>  --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/cd29c165-2c18-48a2-84d1-efcb31473a25%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAJxq84-MRUX3idi1uAFJxy8sWKMaum9on4qSOOn%2BPR8ODdF9qQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Django users Group admin

[Eike Post]

Hello Django users,
does anybody of you know how to get in touch with the Django user group 
admin?
I tried via contact admin and tried emailing to these 
emails: django-users+ad...@googlegroups.com 
django-users+ow...@googlegroups.com. 
But nothing worked so far.
Any suggestions?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cd29c165-2c18-48a2-84d1-efcb31473a25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Squashed migration

[Cherie Pun]

Hi,

I have trying to experiment with squashmigration to see if it will make it 
faster to build the database when running tests. So I have squashed the 
migrations following the instructions on the Django website. However when I 
run the tests, it still uses the original migrations. I thought Django 
automatically uses the squashed one over the separated ones. Is there some 
settings that I have to configure? Also, it says that no optimisation was 
available even though there are a few AddField which should in theory be 
combined into AddModel.

Any help or suggestions will be much appreciated, thanks!

Cherie

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9288958d-0214-4cd2-9b51-dd173a8e83ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django plugin

['Tom Evans' via Django users]

On Thu, Jun 11, 2015 at 8:02 PM, Andreas Kuhne
 wrote:
> Hi all,
>
> I was wondering if there is a plugin application for Django. What I want to
> accomplish is react to different kinds of events on my models and then
> create plugins on the fly for them.
>
> The system I am working on has for example an Order model. When a new Order
> is created, I want to send a notification to the person who created the
> order. I know that I can do this with signals, but I don't want it to
> specifically be tied to a Django application.
>
> I was thinking something along the lines of using RabbitMQ for example to
> post all events there and then be able to react on them later. Has anyone
> done anything like this?
>
> I have seen Celery, but as I understand that, it takes some method to run
> like a delayed job?
>
> Regards,
>
> Andréas
>

Celery is (usually) built on top of an AMQP broker. AMQP was developed
to support High Frequency Trading (HFT) and is ideal for publishing
events and taking actions based upon them. I'd suggest reading this
blog post:

http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

and then the docs for Kombu, which is an excellent messaging library for python.

http://kombu.readthedocs.org/en/latest/

AMQP is not the only message bus, but we've had great results with it
(using rabbitmq).

Cheers

Tom

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFHbX1JEb08O0PMdzEBC0%3Dq8LRVZcHz11PPg067aSby7YhaLjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.