Signal receivers must accept keyword arguments

[daehee]

After a recent Django trunk update, I am getting the following error:

AssertionError: Signal receivers must accept keyword arguments
(**kwargs).

Could it be linked to this revision?
http://code.djangoproject.com/browser/django/trunk/django/dispatch/dispatcher.py?rev=8223

Just a heads up.. if this is not the case, please ignore.

[Bruce Kroeze]

I've got this fixed on the multi-shop branch, it is a fairly extensive update, so I suggest people just wait to update Django until that branch merges.

--
Bruce Kroeze
http://solidsitesolutions.com
Dynamic Designs, Optimized

[Daehee]

Gotcha, thank you. :)

[Bloh]

Hello,

I need to install Django for using another product (ReviewBoard), I'm
facing the same problem (Signal receivers must accept keyword
arguments
(**kwargs). )

Django was not previously installed on my server, what's the best
solution to have a working copy of the library? Is there another
branch that can be checked out?

Thanks for your help

Gilles.

On 7 août, 07:33, "Bruce Kroeze" <bkro...@gmail.com> wrote:
> I've got this fixed on the multi-shop branch, it is a fairly extensive
> update, so I suggest people just wait to update Django until that branch
> merges.
>
> On Wed, Aug 6, 2008 at 10:23 PM, daehee <dae...@gmail.com> wrote:
>
> > After a recent Django trunk update, I am getting the following error:
>
> > AssertionError: Signal receivers must accept keyword arguments
> > (**kwargs).
>
> > Could it be linked to this revision?
>

> >http://code.djangoproject.com/browser/django/trunk/django/dispatch/di...

[John Shaffer]

On Thu, Aug 7, 2008 at 9:27 AM, Bloh <gill...@gmail.com> wrote:
>
> Hello,
>
> I need to install Django for using another product (ReviewBoard), I'm
> facing the same problem (Signal receivers must accept keyword
> arguments
> (**kwargs). )
>
> Django was not previously installed on my server, what's the best
> solution to have a working copy of the library? Is there another
> branch that can be checked out?
>
> Thanks for your help
>
> Gilles.

Run "svn up -r 8032" in your current checkout.

[Frantisek Malina]

Hi Bruce,
When do you plan to merge your multi-shop branch into trunk?
I'd love to check out your implementation as I've been working
independently on my own multi-shop implementation.

Frank
http://vizualbod.com

[Bruce Kroeze]

It is basically ready for beta, the only thing lacking is documentation about the changes.

[Frantisek Malina]

I wouldn't want to hassle you to merge it, if you don't feel like
merging yet. I'd just want a sneak peek :)

On Aug 9, 10:17 pm, "Bruce Kroeze" <bkro...@gmail.com> wrote:
> It is basically ready for beta, the only thing lacking is documentation
> about the changes.
>

> On Sat, Aug 9, 2008 at 1:13 PM, Frantisek Malina <fmal...@gmail.com> wrote:
>
> > Hi Bruce,
> > When do you plan to merge your multi-shop branch into trunk?
> > I'd love to check out your implementation as I've been working
> > independently on my own multi-shop implementation.
>
> > Frank
> >http://vizualbod.com
>
> --

[Bruce Kroeze]

The code is all checked in, just use the multi-shop branch.

[Erik Allik]

Is revision 8032 the latest safe revision of Django to use with the
current trunk of Satchmo?

The "Signal receivers must accept keyword arguments" error first
appears in Django trunk r8223, so r8222 is OK, at least during the
startup of the development server. Any suggestions?

Erik

[Joshua 'jag' Ginsberg]

Current wisdom suggests to use Django r8032 with Satchmo trunk.
Multi-shop will work against Django trunk plus the patch at
http://code.djangoproject.com/ticket/7947 plus Bruce's
http://gosatchmo.com/apps/django-threaded-multihost/ application.

-jag

[Travis Cline]

Not fully tested but here's at least most of the way to trunk
compatibility (as of satchmo r1404 and django r8291).

http://dpaste.com/hold/70613/

[Travis Cline]

> http://dpaste.com/hold/70613/

erh, that's faulty, may as well wait for multishop to land

[Bruce Kroeze]

The only real problem with multishop right now is that Django trunk has a problem with onetoone fields.  I'm using a (very small) patch from http://code.djangoproject.com/ticket/7947 which is marked "accepted", but isn't committed yet.

On Mon, Aug 11, 2008 at 12:01 AM, Travis Cline <travis...@gmail.com> wrote:

> http://dpaste.com/hold/70613/

erh, that's faulty, may as well wait for multishop to land

[Frantisek Malina]

I can't get the threaded_multihost running with my setup:

What is the threaded_multihost for and how to use it.
Is there any documentation, it's used for banjo as well, but there is
no documentation anyway.

I've shot myself in the foot trying to get it running, originally I
just wanted to merge in the code for new signals and I merged in more
than I should.

[Bruce Kroeze]

On Mon, Aug 11, 2008 at 7:00 AM, Frantisek Malina <fma...@gmail.com> wrote:

I can't get the threaded_multihost running with my setup:

What is the threaded_multihost for and how to use it.
Is there any documentation, it's used for banjo as well, but there is
no documentation anyway.

The lack of docs is the reason I haven't released multishop to beta yet.

But, very shortly:

- You need the one from trunk, not the packaged release.  I'll roll a new release when
  I push multihost to beta.

- It provides:

   - threadlocal middleware which holds the current request, allowing python modules to
     get at the current request without having to be passed it in a parameter.

   - site resolution by url.

To use it, add it to your middleware in the position shown in settings-customize.py.  You
*must* make sure that you have a site object with your correct domain name for it to work.
That means you can't just leave it as-is.  For many shops, even live ones, I see people
leaving the default site domain as "example.com." That won't work, and is a bad idea
in any case.

So, if you are developing locally, and you use "localhost:8000" for your test server, then
change site 1 to "localhost."

Once you do this, you can have multiple shops.  They'll resolve by domain name, and
when you go to /settings/ you'll only see settings for that domain name.  When you
are browsing the shop itself you should only see products assigned to that site.

+Bruce Kroeze

[Frantisek Malina]

Thank you, that got me up and running.
I was using the threaded_multihost from the launchpad trunk.
I just had to fix the site object in the DB and settings and I am back
in business.

[Frantisek Malina]

Good news, ticket http://code.djangoproject.com/ticket/7947 is now
fixed.