Django Book

[Timothy Makobu]

The Django book is the best source of understanding Django I have found
http://www.djangobook.com/en/2.0/

However, it's three years old now. Is the info on it still valid?

Is there a plan to update it?

regards,
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Torsten Bronger]

Hallöchen!

Timothy Makobu writes:

> The Django book is the best source of understanding Django I have
> found http://www.djangobook.com/en/2.0/

All books about Django share the same problem: The original
documentation is simply terrific, both for the beginner and the
expert.

Tschö,
Torsten.

-- 
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
  or http://bronger-jmp.appspot.com

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Sami Balbaky]

Hi Tim,

I'm also a fairly new developer in Django, and I found that reading the
book, specifically chapters 1-10, really gave me a solid foundation.
Reading the book in conjunction with https://docs.djangoproject.com/en/1.4/
will give you a very solid footing.

Best,

SB

On Thu, Apr 12, 2012 at 1:09 AM, Torsten Bronger <
bron...@physik.rwth-aachen.de> wrote:

> Hallöchen!
>
> Timothy Makobu writes:
>
> > The Django book is the best source of understanding Django I have
> > found http://www.djangobook.com/en/2.0/
>
> All books about Django share the same problem: The original
> documentation is simply terrific, both for the beginner and the
> expert.
>
> Tschö,
> Torsten.
>
> --
> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>  or http://bronger-jmp.appspot.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Timothy Makobu]

Yes it is. But the book has its place. Or is leaving the book outdated an
indirect way of telling us to use only the docs?


On Thu, Apr 12, 2012 at 11:09 AM, Torsten Bronger <
bron...@physik.rwth-aachen.de> wrote:

> Hallöchen!
>
> Timothy Makobu writes:
>
> > The Django book is the best source of understanding Django I have
> > found http://www.djangobook.com/en/2.0/
>
> All books about Django share the same problem: The original
> documentation is simply terrific, both for the beginner and the
> expert.
>
> Tschö,
> Torsten.
>
> --
> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>  or http://bronger-jmp.appspot.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Timothy Makobu]

Hi, I've been using Django about 4 years now, so the docs and source code
is where I usually get answers these days. But back in the the day when I
started out, the book really helped me understand Django, and I
often recommend it to friends just starting out.

On Thu, Apr 12, 2012 at 11:22 AM, Sami Balbaky wrote:

> Hi Tim,
>
> I'm also a fairly new developer in Django, and I found that reading the
> book, specifically chapters 1-10, really gave me a solid foundation.
> Reading the book in conjunction with
> https://docs.djangoproject.com/en/1.4/  will give you a very solid
> footing.
>
> Best,
>
> SB
>
>
> On Thu, Apr 12, 2012 at 1:09 AM, Torsten Bronger <
> bron...@physik.rwth-aachen.de> wrote:
>
>> Hallöchen!
>>
>> Timothy Makobu writes:
>>
>> > The Django book is the best source of understanding Django I have
>> > found http://www.djangobook.com/en/2.0/
>>
>> All books about Django share the same problem: The original
>> documentation is simply terrific, both for the beginner and the
>> expert.
>>
>> Tschö,
>> Torsten.
>>
>> --
>> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>>  or http://bronger-jmp.appspot.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> 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.
>>
>>
>
>
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Святослав Б]

Documentation is the best source for understanding Django. If your new in
Django - read tutorial:
https://docs.djangoproject.com/en/dev/intro/tutorial01/

List of tutorials: https://code.djangoproject.com/wiki/Tutorials



2012/4/12 Torsten Bronger 

> Hallöchen!
>
> Timothy Makobu writes:
>
> > The Django book is the best source of understanding Django I have
> > found http://www.djangobook.com/en/2.0/
>
> All books about Django share the same problem: The original
> documentation is simply terrific, both for the beginner and the
> expert.
>
> Tschö,
> Torsten.
>
> --
> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>  or http://bronger-jmp.appspot.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Святослав Б]

Your can read book for old versions of Django and then, when your
understand Django - read docs for newer versions.

2012/4/12 Timothy Makobu 

> Yes it is. But the book has its place. Or is leaving the book outdated an
> indirect way of telling us to use only the docs?
>
>
> On Thu, Apr 12, 2012 at 11:09 AM, Torsten Bronger <
> bron...@physik.rwth-aachen.de> wrote:
>
>> Hallöchen!
>>
>> Timothy Makobu writes:
>>
>> > The Django book is the best source of understanding Django I have
>> > found http://www.djangobook.com/en/2.0/
>>
>> All books about Django share the same problem: The original
>> documentation is simply terrific, both for the beginner and the
>> expert.
>>
>> Tschö,
>> Torsten.
>>
>> --
>> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>>  or http://bronger-jmp.appspot.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> 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.
>>
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django ORM - query help

[David]

Hi Jani

That was very helpful. Is there a way to include select_related into that 
query? or do I have to list every single field I would like to return using 
values()?

last_deleted = ModificationLog.objects.values('thing__id', ' 
thing __prefix', ' thing __first_name', ' thing__last_name', ' 
thing__company_name', 'thing__creator', ' thing __created_on', 
'modifier').annotate(deletion_date=Max('modified_on')).filter(appointment__deleted=1).order_by('-deletion_date')[:20]

This for example works, but I don't have access to User. Thing contains a 
FK to the User model, but I'm unable to do in the template {{ 
object_list.creator.get_full_name }}

But I am a lot lot closer than I was before, thank you.

-- 
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/-/XRx3bOc68p0J.
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: Django Book

[Timothy Makobu]

Mmmm, any dev willing to tell us the final word on this?


2012/4/12 Святослав Б 

> Documentation is the best source for understanding Django. If your new in
> Django - read tutorial:
> https://docs.djangoproject.com/en/dev/intro/tutorial01/
>
> List of tutorials: https://code.djangoproject.com/wiki/Tutorials
>
>
>
>
> 2012/4/12 Torsten Bronger 
>
>> Hallöchen!
>>
>> Timothy Makobu writes:
>>
>> > The Django book is the best source of understanding Django I have
>> > found http://www.djangobook.com/en/2.0/
>>
>> All books about Django share the same problem: The original
>> documentation is simply terrific, both for the beginner and the
>> expert.
>>
>> Tschö,
>> Torsten.
>>
>> --
>> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>>  or http://bronger-jmp.appspot.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> 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.
>>
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django ORM - query help

[David]

>
> Hi Jani
>
> That was very helpful. Is there a way to include select_related into that 
> query? or do I have to list every single field I would like to return using 
> values()?
>
> last_deleted = ModificationLog.objects.values('thing__id', ' 
> thing__prefix', ' thing __first_name', ' thing__last_name', ' 
> thing__company_name', 'thing__creator', ' thing __created_on', 
> 'modifier').annotate(deletion_date=Max('modified_on')).filter(thing__deleted=1).order_by('-deletion_date')[:20]
>
> This for example works, but I don't have access to User. Thing contains a 
> FK to the User model, but I'm unable to do in the template {{ 
> object_list.creator.get_full_name }} 
>
>
> But I am a lot lot closer than I was before, thank you.
>
>

-- 
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/-/S4EGADPS2gAJ.
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: Django Book

[Cal Leeming [Simplicity Media Ltd]]

Boy, I've lost count of how many times I've had arguments about books vs
documentation vs learning on your own.

In short, the only way you're going to get updated books is if
technically competent writers spend time writing it - but I doubt many devs
would be interested in re-writing (and essentially duplicating) the
existing documentation - unless they had a passion for books.

Just my two cents worth!

Cal

On Thu, Apr 12, 2012 at 9:51 AM, Timothy Makobu  wrote:

> Mmmm, any dev willing to tell us the final word on this?
>
>
> 2012/4/12 Святослав Б 
>
>> Documentation is the best source for understanding Django. If your new in
>> Django - read tutorial:
>> https://docs.djangoproject.com/en/dev/intro/tutorial01/
>>
>> List of tutorials: https://code.djangoproject.com/wiki/Tutorials
>>
>>
>>
>>
>> 2012/4/12 Torsten Bronger 
>>
>>> Hallöchen!
>>>
>>> Timothy Makobu writes:
>>>
>>> > The Django book is the best source of understanding Django I have
>>> > found http://www.djangobook.com/en/2.0/
>>>
>>> All books about Django share the same problem: The original
>>> documentation is simply terrific, both for the beginner and the
>>> expert.
>>>
>>> Tschö,
>>> Torsten.
>>>
>>> --
>>> Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
>>>  or http://bronger-jmp.appspot.com
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> 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.
>>>
>>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> 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.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django ORM - query help

[akaariai]

On Apr 12, 11:52 am, David  wrote:
> > Hi Jani
>
> > That was very helpful. Is there a way to include select_related into that
> > query? or do I have to list every single field I would like to return using
> > values()?
>
> > last_deleted = ModificationLog.objects.values('thing__id', '
> > thing__prefix', ' thing __first_name', ' thing__last_name', '
> > thing__company_name', 'thing__creator', ' thing __created_on',
> > 'modifier').annotate(deletion_date=Max('modified_on')).filter(thing__deleted=1).order_by('-deletion_date')[:20]
>
> > This for example works, but I don't have access to User. Thing contains a
> > FK to the User model, but I'm unable to do in the template {{
> > object_list.creator.get_full_name }}
>
> > But I am a lot lot closer than I was before, thank you.

One reason why such queries are hard is that they aren't easy to
express using SQL. The left join is correct from ORM perspective: it
can't know that each entry will have at least one log entry attached.
I am not sure how to tell that to the ORM without doing ugly trick
using sql/query.py internals.

If you happen to be using PostgreSQL and Django 1.4 you could probably
do something like this (using DISTINCT ON support added in 1.4):

> ml_objs = ModificationLog.objects.distinct('thing__id').order_by('thing__id', 
> 'modified_on').select_related('thing').

You could then swap the objects around:

> [setattr(ml.thing, 'last_mod', ml) for ml in ml_objs]
> things = [ml.thing for ml in ml_objs]

I am not sure at all the above will work, or that the .distinct() and
order_by() calls are correct for your use case. But DISTINCT ON could
work here...

In general fetching the latest object(s) per related category is a
common operation, and it would be extremely nice if prefetch_related
and/or select_related would support that out of the box. It is a very
commonly repeating pattern: show me the latest mail in each thread,
show me the latest edit for each article, show the highest rating
employee per project and so on. A modification of this theme is "show
me the N latest edits per category" which is pretty hard to do
efficiently using the current ORM APIs.

So, if somebody has ideas how to implement this into prefetch_related/
select_related I am all ears.

 - Anssi

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django ORM - query help

[Jani Tiainen]

12.4.2012 11:51, David kirjoitti:

Hi Jani

That was very helpful. Is there a way to include select_related into
that query? or do I have to list every single field I would like to
return using values()?

last_deleted = ModificationLog.objects.values('thing__id', ' thing
__prefix', ' thing __first_name', ' thing__last_name', '
thing__company_name', 'thing__creator', ' thing __created_on',
'modifier').annotate(deletion_date=Max('modified_on')).filter(appointment__deleted=1).order_by('-deletion_date')[:20]

This for example works, but I don't have access to User. Thing contains
a FK to the User model, but I'm unable to do in the template {{
object_list.creator.get_full_name }}

But I am a lot lot closer than I was before, thank you.

--
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/-/XRx3bOc68p0J.
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.


I suppose that you have to add all fields. I suggest that you install 
django-command-extensions and IPython. Run ./manage.py shell_plus and 
start experimenting.


--

Jani Tiainen



--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
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: Django Book

[Jani Tiainen]

I don't remeber the exact details, but Django book is not part of Django 
project but separate project.


And apparently authors didn't wanted/had time/whatever reason there is 
upgraded documentation along Django.


It would also require lot of upkeeping different versions of books 
(since every version of Django changes/adds something).


And since book is released under GNU Free Documentation License anyone 
can continue contribution to a book.


12.4.2012 11:51, Timothy Makobu kirjoitti:

Mmmm, any dev willing to tell us the final word on this?


2012/4/12 Святослав Б mailto:ad3w.in...@gmail.com>>

Documentation is the best source for understanding Django. If your
new in Django - read tutorial:
https://docs.djangoproject.com/en/dev/intro/tutorial01/

List of tutorials: https://code.djangoproject.com/wiki/Tutorials




2012/4/12 Torsten Bronger mailto:bron...@physik.rwth-aachen.de>>

Hallöchen!

Timothy Makobu writes:

 > The Django book is the best source of understanding Django I have
 > found http://www.djangobook.com/en/2.0/

All books about Django share the same problem: The original
documentation is simply terrific, both for the beginner and the
expert.

Tschö,
Torsten.

--
Torsten BrongerJabber ID:
torsten.bron...@jabber.rwth-aachen.de

  or http://bronger-jmp.appspot.com

--
You received this message because you are subscribed to the
Google Groups "Django users" group.
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.




--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
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.

How can I customise fields in Admin site

[jiaoziren]

Work flexi = Work hours - 7.6

When the user puts 8 in work hours, work flexi should display 0.4 
automatically based on the definition above. Do I need to customise the 
template or modify the models to achieve 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/-/Z8KGy-lxwe8J.
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: Django Book

[kenneth gonsalves]

On Thu, 2012-04-12 at 14:10 +0300, Jani Tiainen wrote:
> And apparently authors didn't wanted/had time/whatever reason there
> is 
> upgraded documentation along Django.
> 
> It would also require lot of upkeeping different versions of books 
> (since every version of Django changes/adds something). 

If I remember correctly, the book was outdated even before it was
released.
-- 
regards
Kenneth Gonsalves

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.

DB queries at import time

[Thomas Guettler]

Hi,

sometimes it happens, that db queries get executed at import time (during 
importing the file by the interpreter).
That's waste of time a resources.

Is there a way to test how many queries get executing during import? I want 
some automated way to detect these db queries.

Example:

def mychoices():
   for obj in MyModel.objects.all(): # this hits the db during import. That's 
not good.
   

class MyForm(forms.Form):
foo=forms.ChoiceField(choices=mychoices())


--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
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: Django Book

[Mehmet Gültaş]

It is valid for Django 1.1. :)

My solution that I used last year, was installing Ubuntu 10.04 LTS 
coming with, guess Django 1.2 or 1.1 not sure.
The book was very solid, easy and did not want to back and fort between 
documentation and book.
After this initial dose of Django book, documentation seemed much more 
easier.


On 12.04.2012 10:44, Timothy Makobu wrote:
The Django book is the best source of understanding Django I have 
found http://www.djangobook.com/en/2.0/


However, it's three years old now. Is the info on it still valid?

Is there a plan to update it?

regards,
Tim

--
You received this message because you are subscribed to the Google 
Groups "Django users" group.

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.


--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
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: Django Book

[Mario Gudelj]

I followed the book in 1.3 and everything worked. It's the best piece of
documentation I've come across. Such great narrative, not too detailed but
detailed enough.

On 12 April 2012 22:10, Mehmet Gültaş  wrote:

> It is valid for Django 1.1. :)
>
> My solution that I used last year, was installing Ubuntu 10.04 LTS coming
> with, guess Django 1.2 or 1.1 not sure.
> The book was very solid, easy and did not want to back and fort between
> documentation and book.
> After this initial dose of Django book, documentation seemed much more
> easier.
>
>
> On 12.04.2012 10:44, Timothy Makobu wrote:
>
>> The Django book is the best source of understanding Django I have found
>> http://www.djangobook.com/en/**2.0/ 
>>
>> However, it's three years old now. Is the info on it still valid?
>>
>> Is there a plan to update it?
>>
>> regards,
>> Tim
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to django-users+unsubscribe@**
>> googlegroups.com .
>> For more options, visit this group at http://groups.google.com/**
>> group/django-users?hl=en
>> .
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to django-users+unsubscribe@**
> googlegroups.com .
> For more options, visit this group at http://groups.google.com/**
> group/django-users?hl=en
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: how to submit data in django's database

[Mario Gudelj]

Have you tried this?:

c = Company()
c.Subject = T
c.save()



On 12 April 2012 02:54, Sophia  wrote:

> Hi all,
>
> I have a question about how to enter data in django's database. I have the
> following Template, in which ' E ' is a variable that get the string:
>
> 
>
> This is my models.py in which I have a class named 'Company' and I want
> this variable 'E' be saved in 'Subject' :
>
> class Company(models.Model):
> Subject = models.CharField(max_length=30)
> start_time = models.DateTimeField()
> end_time = models.DateTimeField()
>
> def __unicode__(self):
> return self.Subject
>
> Then in views.py I wrote something like this to save the variable in
> Subject field, it's incomplete, and I want you to help me about it :
>
> def Text_Box(request):
> T = request.GET.get(E,' ')
> if T:
># I don't know how to make an object of class 'Company' so then I
> save ' T ' in Company.Subject
>  else:
> return render_to_response("Base.html") # Base.html is my basic
> template file
>
> I would really appreciate if you help me with it.
> Thanks in advance.
>
> Sophia
>
>
>
>  --
> 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/-/ChZdnVfKiYIJ.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Ramiro Morales]

On Thu, Apr 12, 2012 at 5:51 AM, Timothy Makobu
 wrote:
> Mmmm, any dev willing to tell us the final word on this?

There is no relationship between the Django project and the
Django book apart from the fact that the tw authors are
so I don't think you will get any official word about book
updates here.

Fortunately there is at least one book from a community member
(Reinout van Rees) in the works:

http://reinout.vanrees.org/weblog/tags/book.html

Regards,

-- 
Ramiro Morales

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django ORM - query help

[David]

Thank you akaariai

That put me on the right track.

Log.objects.distinct('thing__id').order_by('thing__id', 
'-modified_on').select_related().filter(thing__deleted=0)[:20]

By avoiding the use of values() I was able to then use the result as an 
object and access everything I needed.

The above ORM statement however does not look as elegant to read as I have 
come to expect from Django though. The resulting SQL doesn't seem too 
shabby however.

-- 
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/-/ubxdckMp2HwJ.
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: Django Book

[Kurtis Mullins]

I keep a checked out copy of the Django source code and just refer to the
source code, docs, google, the mailing list and IRC for reference, I tried
the book when I first started but it lacked the Class Based Views which I
prefer to use when possible.

Good luck!

On Thu, Apr 12, 2012 at 8:49 AM, Ramiro Morales  wrote:

> On Thu, Apr 12, 2012 at 5:51 AM, Timothy Makobu
>  wrote:
> > Mmmm, any dev willing to tell us the final word on this?
>
> There is no relationship between the Django project and the
> Django book apart from the fact that the tw authors are
> so I don't think you will get any official word about book
> updates here.
>
> Fortunately there is at least one book from a community member
> (Reinout van Rees) in the works:
>
> http://reinout.vanrees.org/weblog/tags/book.html
>
> Regards,
>
> --
> Ramiro Morales
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: DB queries at import time

[Jani Tiainen]

12.4.2012 15:09, Thomas Guettler kirjoitti:

Hi,

sometimes it happens, that db queries get executed at import time
(during importing the file by the interpreter).
That's waste of time a resources.

Is there a way to test how many queries get executing during import? I
want some automated way to detect these db queries.

Example:

def mychoices():
for obj in MyModel.objects.all(): # this hits the db during import.
That's not good.


class MyForm(forms.Form):
foo=forms.ChoiceField(choices=mychoices())




That is because you pass parameter as a function call, so of course 
function must be evaluated. So in your code reads:


Declare class attribute "foo" as a new instance of "forms.ChoiceField" 
with parameter of "choices" with values returned from "mychoices".


So to get rid of that part, you can pass method or a function as a 
parameter and it will be evaluated at the runtime:


class MyForm(forms.Form):
foo=forms.ChoiceField(choices=mychoices)

--

Jani Tiainen


--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
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: Django ORM - query help

[akaariai]

On Apr 12, 4:01 pm, David  wrote:
> The above ORM statement however does not look as elegant to read as I have
> come to expect from Django though. The resulting SQL doesn't seem too
> shabby however.

.distinct(fields) + .order_by() is pretty low level stuff - that is
why it would be nice if there was a dedicated API for queries like
this. Something like:

> qs.first_related('log', order_by='-modified_on')
OUT: qs annotated with log entries.

Turning that into efficient and cross-DB compliant SQL isn't the
easiest thing to do. If you want N first objects instead of one, then
it is going to be even harder.

 - Anssi

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Timothy Makobu]

On Thu, Apr 12, 2012 at 3:45 PM, Mario Gudelj wrote:

> I followed the book in 1.3 and everything worked. It's the best piece of
> documentation I've come across. Such great narrative, not too detailed but
> detailed enough.
>
>
> Yea. I still read chapters randomly as the author can obviously teach
(knows how to lay out complex info simply). It's a shame they decided to
let it rot.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: DB queries at import time

[Thomas Guettler]

Am 12.04.2012 15:25, schrieb Jani Tiainen:

12.4.2012 15:09, Thomas Guettler kirjoitti:

Hi,

sometimes it happens, that db queries get executed at import time
(during importing the file by the interpreter).
That's waste of time a resources.

Is there a way to test how many queries get executing during import? I
want some automated way to detect these db queries.

Example:

def mychoices():
for obj in MyModel.objects.all(): # this hits the db during import.
That's not good.


class MyForm(forms.Form):
foo=forms.ChoiceField(choices=mychoices())




That is because you pass parameter as a function call, so of course function 
must be evaluated. So in your code reads:
...


Yes, I know this. But I work in a team where not everybody is a django expert. I search a way to test for queries which 
happen at import time.


 django debug toolbar does some tricky wrapping of cursor.execute(). I 
guess this could be a solution.

  Thomas

--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
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: Django ORM - query help

[Andre Terra]

On Thu, Apr 12, 2012 at 10:01 AM, David  wrote:

> Log.objects.distinct('thing__id').order_by('thing__id',
> '-modified_on').select_related().filter(thing__deleted=0)[:20]
>
> By avoiding the use of values() I was able to then use the result as an
> object and access everything I needed.
>
> The above ORM statement however does not look as elegant to read as I have
> come to expect from Django though. The resulting SQL doesn't seem too
> shabby however.
>


Django has a tendency of making you write really long lines, but I guess
you could break it into smaller chunks to improve readability.

logs = Log.objects.distinct('thing__id').order_by('thing__id',
'-modified_on')
related = logs.select_related().filter(thing__deleted=0)[:20]


Cheers,
AT

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: DB queries at import time

[Daniel Roseman]

On Thursday, 12 April 2012 13:09:54 UTC+1, guettli wrote:
>
> Hi,
>
> sometimes it happens, that db queries get executed at import time (during 
> importing the file by the interpreter).
> That's waste of time a resources.
>
 
Why? Imports only happen the first time a process accesses a module. A 
process lasts for many requests.

 

> Is there a way to test how many queries get executing during import? I 
> want some automated way to detect these db queries.
>
> Example:
>
> def mychoices():
> for obj in MyModel.objects.all(): # this hits the db during import. 
> That's not good.
> 
>
> class MyForm(forms.Form):
>  foo=forms.ChoiceField(choices=mychoices())
>

The problem caused by this being executed at import time is not a "waste of 
time and resources", but the fact that if you add objects to MyModel, they 
won't appear in the MyForm.foo choices, until the process is restarted - 
which could be several days.
--
DR.

-- 
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/-/XwdAWoqNwv8J.
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: Maybe I'm thinking about this wrong

[hari jayaram]

Hi Don,

Wondering why you dont inherit from just Formview..and define the
success URL to a separate class based ListView. It splits it up into
two class based views with the Formview taking care of returning the
errors on failure. On success it hands off to your Listview based
class that knows which queryset to get and display the response.

I am new to class based views  as well , but I find they are a lot
easier to comprehend looking at the source code for the views
(https://github.com/django/django/blob/master/django/views/generic/edit.py
 and https://github.com/django/django/blob/master/django/views/generic/list.py).

Or maybe you could just inherit from Formview instead of BaseFormView
and ovveride the "get" to handoff to the form and return the response.

Hope this helps..

Hari






BaseFormView implements the same behavior as FormView, but doesn't
include the TemplateResponseMixin.

Mixins

django.views.generic.edit.FormMixin
django.views.generic.edit.ProcessFormView

On Tue, Apr 10, 2012 at 12:40 PM, Dom Armstrong  wrote:
> Im not sure if I am going about this the wrong way.
>
> Trying to learn class based views *sigh* currently seeming more complicated
> and less human readable with no less code currently but I expect most people
> feel that at first.
>
> class HomePage(ListView, BaseFormView):
>     template_name = 'index.html'
>     queryset = Notes.objects.filter(user=1)
>     context_object_name = 'notes'
>     form_class = LoginForm
>     success_url = '/notes/'
>
>     def get_context_date(self, **kwargs):
>         context = super(HomePage, self).get_context_data(**kwargs)
>         context['loginform'] = LoginForm
>         for kwarg in kwargs:
>             context[kwarg] = kwargs[kwarg]
>         return context
>
>     def form_valid(self, form, **kwargs):
>         """do some form stuff"""
>         if "errors with login":
>             kwargs['error'] = 'account not active'
>             kwargs['error_type2'] = 'check details'
>         return self.get_context_data(**kwargs)
>
> what I want to do really is return the errors back to the start as extra
> context, if it was a function I would understand where to send the kwargs..
> currently I get errors regarding missing the original context that would be
> passed to get_context_data since it is only getting my kwargs and not the
> original.
>
> Do I need to be adding
>
> if 'error':
>     error=error
>     return render_to_response('template' {'error':error, 'form':form,
> 'queryset':queryset})
>
> as well as the original context I need, seems messy.
>
> --
> 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/-/f1cCwSjvzFsJ.
> 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.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django Book

[Jani Tiainen]

Btw, you can checkout book as a SVN from
http://djangobook.com/svn/trunk/en/

Maybe we, as a community could import that to bitbucket/github and continue
maintaining it?

On Thu, Apr 12, 2012 at 5:10 PM, Timothy Makobu  wrote:

>
>
> On Thu, Apr 12, 2012 at 3:45 PM, Mario Gudelj wrote:
>
>> I followed the book in 1.3 and everything worked. It's the best piece of
>> documentation I've come across. Such great narrative, not too detailed but
>> detailed enough.
>>
>>
>> Yea. I still read chapters randomly as the author can obviously teach
> (knows how to lay out complex info simply). It's a shame they decided to
> let it rot.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.

constraining one model's attributes with another's

[trubliphone]

All,

I am at my wit's end trying to come up with a structure to do the
following.  I have a "MasterModel" that acts as a template for an
"InstanceModel."  The MasterModel defines a set of name/value pairs.
Each InstanceModel must have a name that corresponds to one of the
names of the MasterModel and a value chosen from the set of values of
that same MasterModel.  So far I have the following code:

  class MasterModel(models.Model):
  name = models.CharField()
  values = MasterValueField()

(MasterValueField is a custom field class that overloads "to_python"
and "value_to_string" such that it stores a string in the database but
returns a list of tuples in Python - of the sort that can be passed to
the "choices" attribute of a field.)

  class InstanceModel(models.Model):
name = models.CharField()
values = models.CharField()

def __init__(self,*args,**kwargs):
  # not sure if this is a good way to do things
  master = kwargs.pop("master",None)
  super(InstanceModel,self).__init__(*args,*kwargs)
  if master:
self._meta.get_field_by_name("name")[0].default = master.name
self._meta.get_field_by_name("value")[0]._choices = master.values

Now I have a class with a relationship to InstanceModel:

  class MyClass(models.Model):
myField = models.CharField()
myOtherField = models.CharField()
instances = models.ManyToManyField("InstanceModel")

There is a form based on MyClass, and a formset based on
InstanceModel.  These both get rendered properly in the view.  What I
am struggling with is figuring out how to initialize the instances.

When I add a new InstanceModel form in the formset, how can I ensure
that its name/value fields are constrained by the name/value fields of
an appropriate MasterModel?

I hope this is clear.

Many thanks for your help.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: constraining one model's attributes with another's

[Jani Tiainen]

So you're basically trying to implement EAV [1]?

There exists few apps that does it for you, like django-eav:

https://github.com/mvpdev/django-eav


[1]
http://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model

On Thu, Apr 12, 2012 at 6:34 PM, trubliphone  wrote:

> All,
>
> I am at my wit's end trying to come up with a structure to do the
> following.  I have a "MasterModel" that acts as a template for an
> "InstanceModel."  The MasterModel defines a set of name/value pairs.
> Each InstanceModel must have a name that corresponds to one of the
> names of the MasterModel and a value chosen from the set of values of
> that same MasterModel.  So far I have the following code:
>
>  class MasterModel(models.Model):
>  name = models.CharField()
>  values = MasterValueField()
>
> (MasterValueField is a custom field class that overloads "to_python"
> and "value_to_string" such that it stores a string in the database but
> returns a list of tuples in Python - of the sort that can be passed to
> the "choices" attribute of a field.)
>
>  class InstanceModel(models.Model):
>name = models.CharField()
>values = models.CharField()
>
>def __init__(self,*args,**kwargs):
>  # not sure if this is a good way to do things
>  master = kwargs.pop("master",None)
>  super(InstanceModel,self).__init__(*args,*kwargs)
>  if master:
>self._meta.get_field_by_name("name")[0].default = master.name
>self._meta.get_field_by_name("value")[0]._choices = master.values
>
> Now I have a class with a relationship to InstanceModel:
>
>  class MyClass(models.Model):
>myField = models.CharField()
>myOtherField = models.CharField()
>instances = models.ManyToManyField("InstanceModel")
>
> There is a form based on MyClass, and a formset based on
> InstanceModel.  These both get rendered properly in the view.  What I
> am struggling with is figuring out how to initialize the instances.
>
> When I add a new InstanceModel form in the formset, how can I ensure
> that its name/value fields are constrained by the name/value fields of
> an appropriate MasterModel?
>
> I hope this is clear.
>
> Many thanks for your help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>


-- 
Jani Tiainen

- Well planned is half done, and a half done has been sufficient before...

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Python Library for Audio Files - Clipping mp3/ogg formats

[Bill Freeman]

There is pysox.  I haven't used it, but bindings for libsox shouldn't
be rocket engineering (rockets haven't been science in a long time).

On 4/11/12, BGMaster  wrote:
> Hi,
>
> I know this isn't a django specific question, but does anyone know of
> a good python library or module for clipping/cutting an mp3 or ogg
> file at a specified start and stop time? The functionality I need is:
>
> 1) take file (example.mp3)
> 2) take start and stop times (hh:mm:ss, hh:mm:ss)
> 3) return new file with audio from given start and stop times
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Filtering ForeignKey Drop Down in Admin Interface

[Setiaman Lee]

Hi,

Thanksit works like champion.

Rgrds,
Setiaman Lee

On Wed, Apr 11, 2012 at 3:00 PM, Святослав Б  wrote:
> Hi!
>
> Override ModelAdmin get_form() method and filter your field.
>
> class MyAdmin(admin.ModelAdmin):
>     def get_form(self, request, obj=None, **kwargs):
>     form = super(MyAdmin,self).get_form(request, obj,**kwargs)
>     form.base_fields['field'].queryset =
> form.base_fields['field'].queryset.filter(user=request.user)
>     return form
>
> 2012/4/11 Setiaman Lee 
>>
>> Hi,
>>
>> I managed to set in the QuerySet of ModelAdmin  to only allow user to
>> see their own record.
>> But when the child model link to parent model using ForeignKey a Drop
>> Down will be automatically created for the respective column.
>> Is there anyway to filter the drop down to only show the records that
>> has been created by the login user?
>>
>>
>> Rgrds,
>> Setiaman Lee.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> 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.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.

Changing validation after changing the model

[BlogueroConnor]

Hello,

I have model and a DB with data. I have to change one field size (lets say, 
from 255 to 4000). The column is called "papers".
I made a South migration, by creating by hand a migration script, and it 
worked, since the size for this column was changed in the DB.
Now I have the column with the size I want, but, in the admin page, I still 
see the field size set to 255 because that is the size of the inputtext in 
the form for this field.
So I overrided the field to make more room for the new data size, by using:

formfield_for_dbfield(self, db_field, **kwargs):

if db_field.name in ('papers',):
return db_field.formfield(widget=forms.Textarea(
attrs={'cols': 80, 'rows': 10},
))

So now I have a bigger form.
But when I put more than 255 chars in it, I get a JS validation error 
telling me that "Ensure this value has at most 255 characters (it has 2332).
"

So the question is how can I change the data size for the JS to take into 
account the new size?

Best,
SB

-- 
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/-/1GsFqbH20_sJ.
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.

ORA-00918: column ambiguously defined.

[Rui Silva]

Hi,

I was working with django 1.3.1 and oracle and i got this error:
ORA-00918: column ambiguously defined.
After some digging in django/db/models/sql/compiler.py i discovered
the bug/error:

My models had a definition according to django sujested naming:

class SampleModel(models.Model):
   my_custom_id = models.AutoField('ID', db_column='MY_CUSTOM_ID'
primary_key=True)
   field2 = models...

class RelatedSampleModel(models.Model):
   id = models.AutoField('ID', primary_key=True)
   sample_model = models.ForeignKey(SampleModel)

As it happens, when we make a query that involves select_related, the
generated query WILL NOT create a column alias for the my_custom_id
column and we will have something like:

SELECT * FROM (
   SELECT ROWNUM AS "_RN", "_SUB".* FROM (
   SELECT
   "SAMPLE_MODEL"."MY_CUSTOM_ID",
   "SAMPLE_MODEL"."FIELD2...",
   "RELATED_SAMPLE_MODEL"."ID",
 
"RELATED_SAMPLE_MODEL"."MY_CUSTOM_ID"
   FROM  "REL"
   INNER JOIN ".)) "_SUB" WHERE ROWNUM <= 21) WHERE
"_RN" > 0'


The problem was the definition of the db_column in uppercase and the
foreignkey as a regular model field, witch resulted in a lowercase
column name in the sql generator.
I solved this error by changing all the names to lowercase. After
that, django correctly defined the column alias:
"RELATED_SAMPLE_MODEL"."MY_CUSTOM_ID" as Col20

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.

tutorial part 1...syncing db

[Brandy]

I am working (again) through the tutorial part 1. I have made changes to 
Engine and Name as specified in the instructions. However, running "python 
manage.py syncdb" continues to return "Please supply the ENGINE value." I 
did not encounter this problem the first time I worked through this 
tutorial.
 
# Django settings for mysite project.

DEBUG = True
TEMPLATE_DEBUG = DEBUG

ADMINS = (
# ('Your Name', 'your_em...@example.com'),
)

MANAGERS = ADMINS

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', # Add 
'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
'NAME': 'c:/program files/bitnami 
djangostack/mysite/sqlite3.db',  # Or path to database 
file if using sqlite3.
'USER': '',  # Not used with sqlite3.
'PASSWORD': '',  # Not used with sqlite3.
'HOST': '',  # Set to empty string for 
localhost. Not used with sqlite3.
'PORT': '',  # Set to empty string for default. 
Not used with sqlite3.
}
}

-- 
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/-/qnfmdfEObKAJ.
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: tutorial part 1...syncing db

[victoria]

On Thu, Apr 12, 2012 at 7:09 PM, Brandy  wrote:
> I am working (again) through the tutorial part 1. I have made changes to
> Engine and Name as specified in the instructions. However, running "python
> manage.py syncdb" continues to return "Please supply the ENGINE value." I
> did not encounter this problem the first time I worked through this
> tutorial.
>
> # Django settings for mysite project.
>
> DEBUG = True
> TEMPLATE_DEBUG = DEBUG
>
> ADMINS = (
>     # ('Your Name', 'your_em...@example.com'),
> )
>
> MANAGERS = ADMINS
>
> DATABASES = {
>     'default': {
>     'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
> 'mysql', 'sqlite3' or 'oracle'.
>     'NAME': 'c:/program files/bitnami
> djangostack/mysite/sqlite3.db',  # Or path to database
> file if using sqlite3.
>     'USER': '',  # Not used with sqlite3.
>     'PASSWORD': '',  # Not used with sqlite3.
>     'HOST': '',  # Set to empty string for
> localhost. Not used with sqlite3.
>     'PORT': '',  # Set to empty string for default.
> Not used with sqlite3.
>     }
> }
>

Your settings seem correct. Which version of django are you using?
Have you checked that the settings.py file is in the correct location
for your django version?

Django 1.4 expects this layout:

mysite/
manage.py
mysite/
__init__.py
settings.py
urls.py
wsgi.py

While Django 1.3 expects this:

mysite/
__init__.py
manage.py
settings.py
urls.py


Since 1.4 was released this seems one of the most common mistakes that
could cause this error.

> --
> 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/-/qnfmdfEObKAJ.
> 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.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.

inconsistent fixture behaviour

[msoulier]

Hi,

I'm doing my development with sqlite and my production deployment with
postgres. I have this model

class Service(models.Model):
name = models.CharField(max_length=256)
description = models.CharField(max_length=4096, default='')
username = models.CharField(max_length=256)
password = models.CharField(max_length=256)
enabled = models.BooleanField(default=False)
access = models.CharField(max_length=16, default="private")

So I created this fixture

[
{
"pk": "ftpd",
"model": "main.service",
"fields": {
"description": "An FTP service for blah blah blah",
"enabled": false,
"access": "private",
"username": "mcd",
"password": ""
}
}
]

When I tried to load the fixture this error occurred

Installing json fixture 'initial_data' from '/home/msoulier/work/mitel-
msl-webproxy/root/etc/e-smith/web/django/webproxy/../webproxy/main/
fixtures'.
Problem installing fixture '/home/msoulier/work/mitel-msl-webproxy/
root/etc/e-smith/web/django/webproxy/../webproxy/main/fixtures/
initial_data.json': Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/django/core/management/commands/
loaddata.py", line 167, in handle
for obj in objects:
  File "/usr/lib/pymodules/python2.6/django/core/serializers/json.py",
line 38, in Deserializer
for obj in PythonDeserializer(simplejson.load(stream), **options):
  File "/usr/lib/pymodules/python2.6/django/core/serializers/
python.py", line 85, in Deserializer
data = {Model._meta.pk.attname :
Model._meta.pk.to_python(d["pk"])}
  File "/usr/lib/pymodules/python2.6/django/db/models/fields/
__init__.py", line 471, in to_python
raise exceptions.ValidationError(self.error_messages['invalid'])
ValidationError: [u'This value must be an integer.']

Huh? I have no integers.

Curious, I changed the false to a for the boolean field, and it works.

?? I use false in other places for boolean fields without issue, why
does it matter here?

Thanks,
Mike

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: inconsistent fixture behaviour

[msoulier]

On Apr 12, 1:44 pm, msoulier  wrote:
>
> class Service(models.Model):
>     name = models.CharField(max_length=256)

*sigh* I should have had primary_key=True on this. Red Herring, sorry.

Mike

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: tutorial part 1...syncing db

[Brandy]

I am in version 1.4. I feel like this is what is happening: I open the file 
to edit it in either Emacs or BlueFish. The file seems to save properly (I 
have verified that the files are being saved to the correct directory), but 
those changes don't seem to be reflected in the files when I access them 
through Django. It is very strange, because when I open the files in an 
editor, they appear to be correct. But django is not picking up on the 
changes for some reason.
 
 

On Thursday, April 12, 2012 12:32:21 PM UTC-5, victoria wrote:

> On Thu, Apr 12, 2012 at 7:09 PM, Brandy  wrote:
> > I am working (again) through the tutorial part 1. I have made changes to
> > Engine and Name as specified in the instructions. However, running 
> "python
> > manage.py syncdb" continues to return "Please supply the ENGINE value." I
> > did not encounter this problem the first time I worked through this
> > tutorial.
> >
> > # Django settings for mysite project.
> >
> > DEBUG = True
> > TEMPLATE_DEBUG = DEBUG
> >
> > ADMINS = (
> > # ('Your Name', 'your_em...@example.com'),
> > )
> >
> > MANAGERS = ADMINS
> >
> > DATABASES = {
> > 'default': {
> > 'ENGINE': 'django.db.backends.sqlite3', # Add 
> 'postgresql_psycopg2',
> > 'mysql', 'sqlite3' or 'oracle'.
> > 'NAME': 'c:/program files/bitnami
> > djangostack/mysite/sqlite3.db',  # Or path to 
> database
> > file if using sqlite3.
> > 'USER': '',  # Not used with sqlite3.
> > 'PASSWORD': '',  # Not used with sqlite3.
> > 'HOST': '',  # Set to empty string for
> > localhost. Not used with sqlite3.
> > 'PORT': '',  # Set to empty string for 
> default.
> > Not used with sqlite3.
> > }
> > }
> >
>
> Your settings seem correct. Which version of django are you using?
> Have you checked that the settings.py file is in the correct location
> for your django version?
>
> Django 1.4 expects this layout:
>
> mysite/
> manage.py
> mysite/
> __init__.py
> settings.py
> urls.py
> wsgi.py
>
> While Django 1.3 expects this:
>
> mysite/
> __init__.py
> manage.py
> settings.py
> urls.py
>
>
> Since 1.4 was released this seems one of the most common mistakes that
> could cause this error.
>
> > --
> > 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/-/qnfmdfEObKAJ.
> > 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.
>
>
On Thursday, April 12, 2012 12:32:21 PM UTC-5, victoria wrote:
>
> On Thu, Apr 12, 2012 at 7:09 PM, Brandy  wrote:
> > I am working (again) through the tutorial part 1. I have made changes to
> > Engine and Name as specified in the instructions. However, running 
> "python
> > manage.py syncdb" continues to return "Please supply the ENGINE value." I
> > did not encounter this problem the first time I worked through this
> > tutorial.
> >
> > # Django settings for mysite project.
> >
> > DEBUG = True
> > TEMPLATE_DEBUG = DEBUG
> >
> > ADMINS = (
> > # ('Your Name', 'your_em...@example.com'),
> > )
> >
> > MANAGERS = ADMINS
> >
> > DATABASES = {
> > 'default': {
> > 'ENGINE': 'django.db.backends.sqlite3', # Add 
> 'postgresql_psycopg2',
> > 'mysql', 'sqlite3' or 'oracle'.
> > 'NAME': 'c:/program files/bitnami
> > djangostack/mysite/sqlite3.db',  # Or path to 
> database
> > file if using sqlite3.
> > 'USER': '',  # Not used with sqlite3.
> > 'PASSWORD': '',  # Not used with sqlite3.
> > 'HOST': '',  # Set to empty string for
> > localhost. Not used with sqlite3.
> > 'PORT': '',  # Set to empty string for 
> default.
> > Not used with sqlite3.
> > }
> > }
> >
>
> Your settings seem correct. Which version of django are you using?
> Have you checked that the settings.py file is in the correct location
> for your django version?
>
> Django 1.4 expects this layout:
>
> mysite/
> manage.py
> mysite/
> __init__.py
> settings.py
> urls.py
> wsgi.py
>
> While Django 1.3 expects this:
>
> mysite/
> __init__.py
> manage.py
> settings.py
> urls.py
>
>
> Since 1.4 was released this seems one of the most common mistakes that
> could cause this error.
>
> > --
> > 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/-/qnfmdfEObKAJ.
> > To post to this group, send email to django-users@g

Re: tutorial part 1...syncing db

[Leonid Toshchev]

Hello.
Try to escape spaces. I don`t check how django work when path have
spaces inside, but i meet same problems in my practice.

p.s. sorry for my bad english.

12 апреля 2012 г. 21:32 пользователь victoria  написал:
> On Thu, Apr 12, 2012 at 7:09 PM, Brandy  wrote:
>> I am working (again) through the tutorial part 1. I have made changes to
>> Engine and Name as specified in the instructions. However, running "python
>> manage.py syncdb" continues to return "Please supply the ENGINE value." I
>> did not encounter this problem the first time I worked through this
>> tutorial.
>>
>> # Django settings for mysite project.
>>
>> DEBUG = True
>> TEMPLATE_DEBUG = DEBUG
>>
>> ADMINS = (
>>     # ('Your Name', 'your_em...@example.com'),
>> )
>>
>> MANAGERS = ADMINS
>>
>> DATABASES = {
>>     'default': {
>>     'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
>> 'mysql', 'sqlite3' or 'oracle'.
>>     'NAME': 'c:/program files/bitnami
>> djangostack/mysite/sqlite3.db',  # Or path to database
>> file if using sqlite3.
>>     'USER': '',  # Not used with sqlite3.
>>     'PASSWORD': '',  # Not used with sqlite3.
>>     'HOST': '',  # Set to empty string for
>> localhost. Not used with sqlite3.
>>     'PORT': '',  # Set to empty string for default.
>> Not used with sqlite3.
>>     }
>> }
>>
>
> Your settings seem correct. Which version of django are you using?
> Have you checked that the settings.py file is in the correct location
> for your django version?
>
> Django 1.4 expects this layout:
>
> mysite/
>    manage.py
>    mysite/
>        __init__.py
>        settings.py
>        urls.py
>        wsgi.py
>
> While Django 1.3 expects this:
>
> mysite/
>    __init__.py
>    manage.py
>    settings.py
>    urls.py
>
>
> Since 1.4 was released this seems one of the most common mistakes that
> could cause this error.
>
>> --
>> 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/-/qnfmdfEObKAJ.
>> 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.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: tutorial part 1...syncing db

[william ratcliff]

Can you post your full code somewhere as a zip?



On Thu, Apr 12, 2012 at 2:33 PM, Leonid Toshchev wrote:

> Hello.
> Try to escape spaces. I don`t check how django work when path have
> spaces inside, but i meet same problems in my practice.
>
> p.s. sorry for my bad english.
>
> 12 апреля 2012 г. 21:32 пользователь victoria  написал:
> > On Thu, Apr 12, 2012 at 7:09 PM, Brandy 
> wrote:
> >> I am working (again) through the tutorial part 1. I have made changes to
> >> Engine and Name as specified in the instructions. However, running
> "python
> >> manage.py syncdb" continues to return "Please supply the ENGINE value."
> I
> >> did not encounter this problem the first time I worked through this
> >> tutorial.
> >>
> >> # Django settings for mysite project.
> >>
> >> DEBUG = True
> >> TEMPLATE_DEBUG = DEBUG
> >>
> >> ADMINS = (
> >> # ('Your Name', 'your_em...@example.com'),
> >> )
> >>
> >> MANAGERS = ADMINS
> >>
> >> DATABASES = {
> >> 'default': {
> >> 'ENGINE': 'django.db.backends.sqlite3', # Add
> 'postgresql_psycopg2',
> >> 'mysql', 'sqlite3' or 'oracle'.
> >> 'NAME': 'c:/program files/bitnami
> >> djangostack/mysite/sqlite3.db',  # Or path to
> database
> >> file if using sqlite3.
> >> 'USER': '',  # Not used with sqlite3.
> >> 'PASSWORD': '',  # Not used with sqlite3.
> >> 'HOST': '',  # Set to empty string for
> >> localhost. Not used with sqlite3.
> >> 'PORT': '',  # Set to empty string for
> default.
> >> Not used with sqlite3.
> >> }
> >> }
> >>
> >
> > Your settings seem correct. Which version of django are you using?
> > Have you checked that the settings.py file is in the correct location
> > for your django version?
> >
> > Django 1.4 expects this layout:
> >
> > mysite/
> >manage.py
> >mysite/
> >__init__.py
> >settings.py
> >urls.py
> >wsgi.py
> >
> > While Django 1.3 expects this:
> >
> > mysite/
> >__init__.py
> >manage.py
> >settings.py
> >urls.py
> >
> >
> > Since 1.4 was released this seems one of the most common mistakes that
> > could cause this error.
> >
> >> --
> >> 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/-/qnfmdfEObKAJ.
> >> 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.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Django users" group.
> > 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.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: [JOB] Urgent - PHP/Python Developer needed

[Cal Leeming [Simplicity Media Ltd]]

Further update on this - budget has changed so, we can now offer a higher
rate and a part time alternative.

* 1500$/month for 70 hours (20$/hour)
* 2000$/month for 100 hours (20$/hour)

Thanks

Cal

On Tue, Apr 10, 2012 at 9:31 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:

> Hi all,
>
> Another urgent position has come up in our company, applicant needs to
> have some experience with using Django but must also be comfortable with
> PHP (our clients are a 50/50 split between PHP and Django).
>
> --
>
> Simplicity Media Ltd are an established UK company providing bespoke IT
> solutions for a variety of clients across the globe.
>
> We are currently looking for a flexible and diverse developer to maintain
> and extend our existing PHP deployments.
>
> Our solutions are high volume (peaking at around 5000 requests/minute),
> with extremely large databases (400 million+ rows) and large content
> servers (15TB+ of media files).
>
> The successful candidate should have at least 2 years commercial
> experience, be fluent OOP, and have a general understanding of what it
> means to be a good programmer.
>
> We're looking for a real person with real emotion, not a corporate robot -
> and being a team player is absolutely critical. Our company attitude is
> firm but fair, we encourage a healthy mixture of fun/work, and we even have
> a 'NSFW' IRC channel!
>
> Essential skills:
> * PHP 5.x (OOP)
> * MySQL
> * Linux (Debian)
> * Bash (shell/ssh etc)
>
> Desired (non-essential) skills:
> * MongoDB
> * Redhat
> * Percona
> * Memcache
> * Redis
> * Python
>
> Desired (non-essential) experience:
> * CodeIgniter (PHP)
> * TubeX (PHP)
> * Django (Python)
> * JIRA (Atlassian)
> * Basecamp
> * Zendesk
> * Livechat
>
> MINIMUM CRITERIA:
> * MUST be able to work on either EST or GMT+0 timezone
> * MUST be able to work 30+ hours a week.
> * MUST be comfortable working on 18+ sites.
> * MUST be fluent in written & spoken English
>
> The position is full time, offering around $2000/month (roughly
> £1200/month) for the right candidate - price/hours are negotiable.
>
> This position MUST be filled by 15th April 2012.
>
> When applying, please also include a cover note explaining why you feel
> you would be suitable for this role.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.

URL Routing in the Admin App

[jws]

My sad story- I have inherited an app developed by a third party that
I am deploying and I'm having strange issues with it. The last known
working configuration was lost when a virtual host was inadvertently
destroyed.

The specific problem is that the admin app is not creating urls to
pages correctly. I can login to the app as the superuser and connect
to the base admin url. Let's call it

 http://www.mysite.com/admin

When I click the link to add a group, the url I get is

 http://www.mysite.com/admin/auth/user/add/

which appears to be correct, but the page that is displayed is the
same base admin page. If I click the link again, I get the url

 http://www.mysite.com/admin/auth/user/add/auth/user/add/

Which, while entertaining, is clearly wrong. Again, I get the base
admin page. This occurs for all the objects in the model. I tried
running the development server rather than apache httpd(same result),
so the issue is part of the Django app itself.

I did notice that in the urls.py, the regex for the admin app looks
like this -
(r'^admin/(.*)', include(admin.site.urls)) , which is not the
default.

This is Django 1.2.3 and user profiles are in the mix somehow, though
I'm not familiar with that feature. People are supposed to be routed
to different pages based on group membership. I don't think that
applies to the admin, but thought it should be mentioned.

I'm out of good ideas, any suggestions would be appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: tutorial part 1...syncing db

[william ratcliff]

Hi Brandy,

I downloaded your project modified the beginning to the following:

# Django settings for mysite project.

import os,sys
HOMEDIR=os.path.dirname(__file__)
DEBUG = True
TEMPLATE_DEBUG = DEBUG

ADMINS = (
# ('Your Name', 'your_em...@example.com'),
)

MANAGERS = ADMINS

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', # Add
'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
'NAME': os.path.join(HOMEDIR,'testdb'),  # Or
path to database file if using sqlite3.
'USER': '',  # Not used with sqlite3.
'PASSWORD': '',  # Not used with sqlite3.
'HOST': '',  # Set to empty string for
localhost. Not used with sqlite3.
'PORT': '',  # Set to empty string for default.
Not used with sqlite3.
}
}

It works under the django 1.4 that I just pulled onto a "virgin" windows 7
box. My suspicion is that in your engine file, you wanted to use:
r'c:/program files/bitnami djangostack/mysite/sqlite3.db'
instead of:
'c:/program files/bitnami djangostack/mysite/sqlite3.db',

This is assuming that you have read/write permissions to that directory,
etc.I prefer the pattern that I used of putting the sqllite database
relative to __file__ because it is easier to move it between machines.
So, for example, if I develop on a mac (or windows), when I deploy to linux
(not so much for the database) for production, I don't have to manipulate
the path throughout the code...Later, if I need to find something relative
to the project root, I can then do a:

from django.conf import settings
and grab settings.HOME as the base directory

Best,
William
(btw. I placed the directory in c:\mysite for my test

so you have:
-- denotes a mysite directory


c:\mysite
manage.py
--mysite
  __init__.py
  settings.py
  testdb
  urls.py
  wsgi.py


)



2012/4/12 Brandy 

> This is the whole directory.
>
>
> On Thursday, April 12, 2012 2:00:24 PM UTC-5, William Ratcliff wrote:
>
>> Can you post your full code somewhere as a zip?
>>
>>
>>
>> On Thu, Apr 12, 2012 at 2:33 PM, Leonid Toshchev wrote:
>>
>>> Hello.
>>> Try to escape spaces. I don`t check how django work when path have
>>> spaces inside, but i meet same problems in my practice.
>>>
>>> p.s. sorry for my bad english.
>>>
>>> 12 апреля 2012 г. 21:32 пользователь victoria 
>>> написал:
>>> > On Thu, Apr 12, 2012 at 7:09 PM, Brandy 
>>> wrote:
>>> >> I am working (again) through the tutorial part 1. I have made changes
>>> to
>>> >> Engine and Name as specified in the instructions. However, running
>>> "python
>>> >> manage.py syncdb" continues to return "Please supply the ENGINE
>>> value." I
>>> >> did not encounter this problem the first time I worked through this
>>> >> tutorial.
>>> >>
>>> >> # Django settings for mysite project.
>>> >>
>>> >> DEBUG = True
>>> >> TEMPLATE_DEBUG = DEBUG
>>> >>
>>> >> ADMINS = (
>>> >> # ('Your Name', 'your_em...@example.com'),
>>> >> )
>>> >>
>>> >> MANAGERS = ADMINS
>>> >>
>>> >> DATABASES = {
>>> >> 'default': {
>>> >> 'ENGINE': 'django.db.backends.sqlite3', # Add
>>> 'postgresql_psycopg2',
>>> >> 'mysql', 'sqlite3' or 'oracle'.
>>> >> 'NAME': 'c:/program files/bitnami
>>> >> djangostack/mysite/sqlite3.db'**,  # Or path to
>>> database
>>> >> file if using sqlite3.
>>> >> 'USER': '',  # Not used with sqlite3.
>>> >> 'PASSWORD': '',  # Not used with sqlite3.
>>> >> 'HOST': '',  # Set to empty string for
>>> >> localhost. Not used with sqlite3.
>>> >> 'PORT': '',  # Set to empty string for
>>> default.
>>> >> Not used with sqlite3.
>>> >> }
>>> >> }
>>> >>
>>> >
>>> > Your settings seem correct. Which version of django are you using?
>>> > Have you checked that the settings.py file is in the correct location
>>> > for your django version?
>>> >
>>> > Django 1.4 expects this layout:
>>> >
>>> > mysite/
>>> >manage.py
>>> >mysite/
>>> >__init__.py
>>> >settings.py
>>> >urls.py
>>> >wsgi.py
>>> >
>>> > While Django 1.3 expects this:
>>> >
>>> > mysite/
>>> >__init__.py
>>> >manage.py
>>> >settings.py
>>> >urls.py
>>> >
>>> >
>>> > Since 1.4 was released this seems one of the most common mistakes that
>>> > could cause this error.
>>> >
>>> >> --
>>> >> 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/-/**qnfmdfEObKAJ
>>> .
>>> >> To post to this group, send email to django-users@googlegroups.com.
>>> >> To unsubscribe from this group, send email to
>>> >> django-users+unsubscribe@**googlegroups.com
>>> .
>>> >>

Re: [JOB] Urgent - PHP/Python Developer needed

[ionic drive]

great:

I think this is a good sellery for India if you add some bonuses.

good luck


On Thu, 2012-04-12 at 20:27 +0100, Cal Leeming [Simplicity Media Ltd]
wrote:

> Further update on this - budget has changed so, we can now offer
> a higher rate and a part time alternative.
> 
> 
> 
> * 1500$/month for 70 hours (20$/hour)
> * 2000$/month for 100 hours (20$/hour)
> 
> 
> Thanks
> 
> 
> Cal
> 
> 
> On Tue, Apr 10, 2012 at 9:31 PM, Cal Leeming [Simplicity Media Ltd]
>  wrote:
> 
> Hi all,
> 
> 
> 
> Another urgent position has come up in our company, applicant
> needs to have some experience with using Django but must also
> be comfortable with PHP (our clients are a 50/50 split between
> PHP and Django).
> 
> 
> --
> 
> 
> Simplicity Media Ltd are an established UK company providing
> bespoke IT solutions for a variety of clients across the
> globe.
> 
> We are currently looking for a flexible and diverse developer
> to maintain and extend our existing PHP deployments.
> 
> Our solutions are high volume (peaking at around 5000
> requests/minute), with extremely large databases (400 million+
> rows) and large content servers (15TB+ of media files).
> 
> The successful candidate should have at least 2 years
> commercial experience, be fluent OOP, and have a general
> understanding of what it means to be a good programmer.
> 
> We're looking for a real person with real emotion, not a
> corporate robot - and being a team player is absolutely
> critical. Our company attitude is firm but fair, we encourage
> a healthy mixture of fun/work, and we even have a 'NSFW' IRC
> channel!
> 
> Essential skills:
> * PHP 5.x (OOP)
> * MySQL
> * Linux (Debian)
> * Bash (shell/ssh etc)
> 
> Desired (non-essential) skills:
> * MongoDB
> * Redhat
> * Percona
> * Memcache
> * Redis
> * Python
> 
> Desired (non-essential) experience:
> * CodeIgniter (PHP)
> * TubeX (PHP)
> * Django (Python)
> * JIRA (Atlassian)
> * Basecamp
> * Zendesk
> * Livechat
> 
> MINIMUM CRITERIA:
> * MUST be able to work on either EST or GMT+0 timezone
> * MUST be able to work 30+ hours a week.
> * MUST be comfortable working on 18+ sites.
> * MUST be fluent in written & spoken English
> 
> The position is full time, offering around $2000/month
> (roughly £1200/month) for the right candidate - price/hours
> are negotiable.
> 
> This position MUST be filled by 15th April 2012.
> 
> When applying, please also include a cover note explaining why
> you feel you would be suitable for this role.
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> 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.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: DB queries at import time

[Matt Schinckel]

If you install django-devserver, and enable SQL queries in the console, then
every query will be displayed as it happens, and you should be able to 
track them
down.

Matt.

-- 
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/-/ELbykFSSiFwJ.
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: tutorial part 1...syncing db

[Brandy]

FINALLY! I used your modifications and adjusted the security settings of 
the directory (twice). And now it works. Thank you everyone for taking the 
time to look at my code!
 
Brandy

On Thursday, April 12, 2012 3:13:58 PM UTC-5, William Ratcliff wrote:

> Hi Brandy,
>
> I downloaded your project modified the beginning to the following:
>
> # Django settings for mysite project.
>
> import os,sys
> HOMEDIR=os.path.dirname(__file__)
> DEBUG = True
> TEMPLATE_DEBUG = DEBUG
>
> ADMINS = (
> # ('Your Name', 'your_em...@example.com'),
> )
>
> MANAGERS = ADMINS
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3', # Add 
> 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': os.path.join(HOMEDIR,'testdb'),  # Or 
> path to database file if using sqlite3.
> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for 
> localhost. Not used with sqlite3.
> 'PORT': '',  # Set to empty string for 
> default. Not used with sqlite3.
> }
> }
>
> It works under the django 1.4 that I just pulled onto a "virgin" windows 7 
> box. My suspicion is that in your engine file, you wanted to use:
> r'c:/program files/bitnami djangostack/mysite/sqlite3.db'
> instead of:
> 'c:/program files/bitnami djangostack/mysite/sqlite3.db', 
>
> This is assuming that you have read/write permissions to that directory, 
> etc.I prefer the pattern that I used of putting the sqllite database 
> relative to __file__ because it is easier to move it between machines.   
> So, for example, if I develop on a mac (or windows), when I deploy to linux 
> (not so much for the database) for production, I don't have to manipulate 
> the path throughout the code...Later, if I need to find something relative 
> to the project root, I can then do a:
>
> from django.conf import settings
> and grab settings.HOME as the base directory
>
> Best,
> William
> (btw. I placed the directory in c:\mysite for my test
>
> so you have:
> -- denotes a mysite directory
>
>
> c:\mysite
> manage.py
> --mysite
>   __init__.py
>   settings.py
>   testdb
>   urls.py
>   wsgi.py
>
>
> )
>
>
>
> 2012/4/12 Brandy 
>
>> This is the whole directory.
>>  
>>
>> On Thursday, April 12, 2012 2:00:24 PM UTC-5, William Ratcliff wrote:
>>
>>> Can you post your full code somewhere as a zip?
>>>
>>>
>>>
>>> On Thu, Apr 12, 2012 at 2:33 PM, Leonid Toshchev wrote:
>>>
 Hello.
 Try to escape spaces. I don`t check how django work when path have
 spaces inside, but i meet same problems in my practice.

 p.s. sorry for my bad english.

 12 апреля 2012 г. 21:32 пользователь victoria  
 написал:
 > On Thu, Apr 12, 2012 at 7:09 PM, Brandy  
 wrote:
 >> I am working (again) through the tutorial part 1. I have made 
 changes to
 >> Engine and Name as specified in the instructions. However, running 
 "python
 >> manage.py syncdb" continues to return "Please supply the ENGINE 
 value." I
 >> did not encounter this problem the first time I worked through this
 >> tutorial.
 >>
 >> # Django settings for mysite project.
 >>
 >> DEBUG = True
 >> TEMPLATE_DEBUG = DEBUG
 >>
 >> ADMINS = (
 >> # ('Your Name', 'your_em...@example.com'),
 >> )
 >>
 >> MANAGERS = ADMINS
 >>
 >> DATABASES = {
 >> 'default': {
 >> 'ENGINE': 'django.db.backends.sqlite3', # Add 
 'postgresql_psycopg2',
 >> 'mysql', 'sqlite3' or 'oracle'.
 >> 'NAME': 'c:/program files/bitnami
 >> djangostack/mysite/sqlite3.db'**,  # Or path to 
 database
 >> file if using sqlite3.
 >> 'USER': '',  # Not used with sqlite3.
 >> 'PASSWORD': '',  # Not used with sqlite3.
 >> 'HOST': '',  # Set to empty string for
 >> localhost. Not used with sqlite3.
 >> 'PORT': '',  # Set to empty string for 
 default.
 >> Not used with sqlite3.
 >> }
 >> }
 >>
 >
 > Your settings seem correct. Which version of django are you using?
 > Have you checked that the settings.py file is in the correct location
 > for your django version?
 >
 > Django 1.4 expects this layout:
 >
 > mysite/
 >manage.py
 >mysite/
 >__init__.py
 >settings.py
 >urls.py
 >wsgi.py
 >
 > While Django 1.3 expects this:
 >
 > mysite/
 >__init__.py
 >manage.py
 >settings.py
 >urls.py
 >
 >
 > Since 1.4 was released this seems one of the most common mistakes that
 > could cause this error.
 >
>>>

Re: URL Routing in the Admin App

[Russell Keith-Magee]

Hi,

This bug sounds familiar, from back in the days when Django's admin started 
migrating to named URLs in the admin.

The regex you've got for the admin page is the source of the problem. What 
you've got is a weird hybrid between the old style:

(r'^admin/(.*)', admin.site.root), 

and the new style:

(r'^admin/', include(admin.site.urls)),

If you drop the (.*) portion from your admin pattern, that should fix the 
problem.

Yours,
Russ Magee %-)


On Friday, 13 April 2012 at 3:29 AM, jws wrote:

> My sad story- I have inherited an app developed by a third party that
> I am deploying and I'm having strange issues with it. The last known
> working configuration was lost when a virtual host was inadvertently
> destroyed.
> 
> The specific problem is that the admin app is not creating urls to
> pages correctly. I can login to the app as the superuser and connect
> to the base admin url. Let's call it
> 
> http://www.mysite.com/admin
> 
> When I click the link to add a group, the url I get is
> 
> http://www.mysite.com/admin/auth/user/add/
> 
> which appears to be correct, but the page that is displayed is the
> same base admin page. If I click the link again, I get the url
> 
> http://www.mysite.com/admin/auth/user/add/auth/user/add/
> 
> Which, while entertaining, is clearly wrong. Again, I get the base
> admin page. This occurs for all the objects in the model. I tried
> running the development server rather than apache httpd(same result),
> so the issue is part of the Django app itself.
> 
> I did notice that in the urls.py, the regex for the admin app looks
> like this -
> (r'^admin/(.*)', include(admin.site.urls)) , which is not the
> default.
> 
> This is Django 1.2.3 and user profiles are in the mix somehow, though
> I'm not familiar with that feature. People are supposed to be routed
> to different pages based on group membership. I don't think that
> applies to the admin, but thought it should be mentioned.
> 
> I'm out of good ideas, any suggestions would be appreciated.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com 
> (mailto:django-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com 
> (mailto:django-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: ORA-00918: column ambiguously defined.

[Russell Keith-Magee]

Hi Rui,

Sounds like a bug to me; please open a ticket describing the problem you have 
found.

Yours,
Russ Magee %-)



On Friday, 13 April 2012 at 12:48 AM, Rui Silva wrote:

> Hi,
> 
> I was working with django 1.3.1 and oracle and i got this error:
> ORA-00918: column ambiguously defined.
> After some digging in django/db/models/sql/compiler.py i discovered
> the bug/error:
> 
> My models had a definition according to django sujested naming:
> 
> class SampleModel(models.Model):
> my_custom_id = models.AutoField('ID', db_column='MY_CUSTOM_ID'
> primary_key=True)
> field2 = models...
> 
> class RelatedSampleModel(models.Model):
> id = models.AutoField('ID', primary_key=True)
> sample_model = models.ForeignKey(SampleModel)
> 
> As it happens, when we make a query that involves select_related, the
> generated query WILL NOT create a column alias for the my_custom_id
> column and we will have something like:
> 
> SELECT * FROM (
> SELECT ROWNUM AS "_RN", "_SUB".* FROM (
> SELECT
> "SAMPLE_MODEL"."MY_CUSTOM_ID",
> "SAMPLE_MODEL"."FIELD2...",
> "RELATED_SAMPLE_MODEL"."ID",
> 
> "RELATED_SAMPLE_MODEL"."MY_CUSTOM_ID"
> FROM "REL"
> INNER JOIN ".)) "_SUB" WHERE ROWNUM <= 21) WHERE
> "_RN" > 0'
> 
> 
> The problem was the definition of the db_column in uppercase and the
> foreignkey as a regular model field, witch resulted in a lowercase
> column name in the sql generator.
> I solved this error by changing all the names to lowercase. After
> that, django correctly defined the column alias:
> "RELATED_SAMPLE_MODEL"."MY_CUSTOM_ID" as Col20
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com 
> (mailto:django-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com 
> (mailto:django-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: Django ORM - query help

[Russell Keith-Magee]

On Thursday, 12 April 2012 at 10:47 PM, Andre Terra wrote:

> On Thu, Apr 12, 2012 at 10:01 AM, David  (mailto:cthl...@gmail.com)> wrote:
> > Log.objects.distinct('thing__id').order_by('thing__id', 
> > '-modified_on').select_related().filter(thing__deleted=0)[:20]
> > 
> > By avoiding the use of values() I was able to then use the result as an 
> > object and access everything I needed. 
> > 
> > The above ORM statement however does not look as elegant to read as I have 
> > come to expect from Django though. The resulting SQL doesn't seem too 
> > shabby however. 
> 
> 
> Django has a tendency of making you write really long lines, but I guess you 
> could break it into smaller chunks to improve readability.
> 
> logs = Log.objects.distinct('thing__id').order_by('thing__id', 
> '-modified_on') 
> related = logs.select_related().filter(thing__deleted=0)[:20]

The other option is to find ways to break the line using Python's own syntax. 
e.g.:

Log.objects.distinct(
'thing__id'
).order_by(
'thing__id', '-modified_on'
).select_related(
).filter(
thing__deleted=0
)[:20]


Yours,
Russ Magee %-)


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: [JOB] Urgent - PHP/Python Developer needed

[Gerald Klein]

Hi, I have over 20 years in the software business, I have worked for the
big 6 back in the day of the dotcom crash. I am in the states so schedule
is not a problem. I am looking for steady work, I am always available I
don't do any onsite work. This spot is a perfect fit. The essentials are a
slam dunk and I have more then a working knowledge of most of the rest.
Please look over my resume and for more information please visit my web
site http://www.geraldklein.com. I can be contacted at the information
below.

Thank you for your kind consideration.

Gerald Klein


On Thu, Apr 12, 2012 at 2:27 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:

> Further update on this - budget has changed so, we can now offer a higher
> rate and a part time alternative.
>
> * 1500$/month for 70 hours (20$/hour)
> * 2000$/month for 100 hours (20$/hour)
>
> Thanks
>
> Cal
>
> On Tue, Apr 10, 2012 at 9:31 PM, Cal Leeming [Simplicity Media Ltd] <
> cal.leem...@simplicitymedialtd.co.uk> wrote:
>
>> Hi all,
>>
>> Another urgent position has come up in our company, applicant needs to
>> have some experience with using Django but must also be comfortable with
>> PHP (our clients are a 50/50 split between PHP and Django).
>>
>> --
>>
>> Simplicity Media Ltd are an established UK company providing bespoke IT
>> solutions for a variety of clients across the globe.
>>
>> We are currently looking for a flexible and diverse developer to maintain
>> and extend our existing PHP deployments.
>>
>> Our solutions are high volume (peaking at around 5000 requests/minute),
>> with extremely large databases (400 million+ rows) and large content
>> servers (15TB+ of media files).
>>
>> The successful candidate should have at least 2 years commercial
>> experience, be fluent OOP, and have a general understanding of what it
>> means to be a good programmer.
>>
>> We're looking for a real person with real emotion, not a corporate robot
>> - and being a team player is absolutely critical. Our company attitude is
>> firm but fair, we encourage a healthy mixture of fun/work, and we even have
>> a 'NSFW' IRC channel!
>>
>> Essential skills:
>> * PHP 5.x (OOP)
>> * MySQL
>> * Linux (Debian)
>> * Bash (shell/ssh etc)
>>
>> Desired (non-essential) skills:
>> * MongoDB
>> * Redhat
>> * Percona
>> * Memcache
>> * Redis
>> * Python
>>
>> Desired (non-essential) experience:
>> * CodeIgniter (PHP)
>> * TubeX (PHP)
>> * Django (Python)
>> * JIRA (Atlassian)
>> * Basecamp
>> * Zendesk
>> * Livechat
>>
>> MINIMUM CRITERIA:
>> * MUST be able to work on either EST or GMT+0 timezone
>> * MUST be able to work 30+ hours a week.
>> * MUST be comfortable working on 18+ sites.
>> * MUST be fluent in written & spoken English
>>
>> The position is full time, offering around $2000/month (roughly
>> £1200/month) for the right candidate - price/hours are negotiable.
>>
>> This position MUST be filled by 15th April 2012.
>>
>> When applying, please also include a cover note explaining why you feel
>> you would be suitable for this role.
>>
>>
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>



-- 

Gerald Klein DBA

contac...@geraldklein.com

www.geraldklein.com 

j...@zognet.com

708-599-0352


Linux registered user #548580

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.



Gerald Klein.doc
Description: MS-Word document

[JOB] Django Programmers

[Martino]

Good day,

I am Martin Vincent, CTO for ISolutionspro, an internet business
consulting firm that specializes in custom online marketing and web
software development.

Right now we are searchng for five or more years experienced Python
Django programmers to work with us developing a facebook app.

We plan to interview some of them, in order to realize that they know
what we need and then prosecute with a contract.

I would appreciate if you send me a response as fast as you can,
thanks.

--
Best,

Martin Vincent
Chief Technology Officer

iSolutionspro.com
Internet Business Consulting

Email: mvinc...@isolutionspro.com, dsala...@isolutionspro.com,
mmalaga...@isolutionspro.com

Las Vegas Office:

Main:702.518.4113

Direct: 310.751.0833

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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: [JOB] Django Programmers

[Mark Phillips]

That's not very nice to prosecute potential employees.at least wait
until you hire them and they do something wrong.;)

Mark

On Thu, Apr 12, 2012 at 5:52 PM, Martino  wrote:

> Good day,
>
> I am Martin Vincent, CTO for ISolutionspro, an internet business
> consulting firm that specializes in custom online marketing and web
> software development.
>
> Right now we are searchng for five or more years experienced Python
> Django programmers to work with us developing a facebook app.
>
> We plan to interview some of them, in order to realize that they know
> what we need and then prosecute with a contract.
>
> I would appreciate if you send me a response as fast as you can,
> thanks.
>
> --
> Best,
>
> Martin Vincent
> Chief Technology Officer
>
> iSolutionspro.com
> Internet Business Consulting
>
> Email: mvinc...@isolutionspro.com, dsala...@isolutionspro.com,
> mmalaga...@isolutionspro.com
>
> Las Vegas Office:
>
> Main:702.518.4113
>
> Direct: 310.751.0833
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> 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.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
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.