Re: Need Django Developer urgent

[haur]

hello , i'am in china

i'am  a  pythoner ~~


uses python, django, nginx and so on.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Reduce bug triage overhead: DjangoAwesomeBot

[Henrique Romano]

On May 5, 2009, at 7:03 PM, Jacob Kaplan-Moss wrote:

>
> On Tue, May 5, 2009 at 11:56 PM, Almad  wrote:
>> Cool for me, but have enough pet projects so now, but if anyone have
>> spare weekend to implement it? :)
>
> Unfortunately, Anyone doesn't have a lot of free time these days (nor
> does his brother, Someone).

It seems a good idea, and IMHO we should try to start implementing  
something.  I've created a project at google code named django-triage- 
bot, if anyone is interested.

Is everybody happy with this triage automation?

--
Henrique

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Reduce bug triage overhead: DjangoAwesomeBot

[Jacob Kaplan-Moss]

On Tue, May 5, 2009 at 11:56 PM, Almad  wrote:
> Cool for me, but have enough pet projects so now, but if anyone have
> spare weekend to implement it? :)

Unfortunately, Anyone doesn't have a lot of free time these days (nor
does his brother, Someone).

No, but on a serious note: ideas are cheap; code and time are
expensive. Ideas like these *always* sound good, but it's impossible
to judge without a proof-of-concept. Things don't "just happen" in
open source; they happen when motivated people write them, usually
without anyone's permission or say-so.

Jacob

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: New to open source dev

[Jacob Kaplan-Moss]

On Tue, May 5, 2009 at 10:24 PM, Joshua Russo  wrote:
> I have been tinkering with some custom objects for db fields, form
> fields, and widgets and have seen one or two things that might be nice
> enhancements to the base objects. How exactly does the process of
> contributing work?

Glad you're interested! The best way to learn about how our developer
community works is to checkout our guide to contributing to Django:
http://docs.djangoproject.com/en/dev/internals/contributing/

Good luck,

Jacob

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Reduce bug triage overhead: DjangoAwesomeBot

[Almad]

Hi,

earlier today, someone was speaking at EuroDjangoCon about how boring
it is to triage tickets (apply against trunk, run tests, etc. etc.)
and that's why it's not progressing smoothly.

I'm thinking: Why not automate this?

Simple bot that will log in to it's trac account, look for "ready for
bot" triage, get ticket, apply tests from the patch against trunk, run
it, make sure it fails, apply whole patch against trunk, make sure
test passed, add a comment, move to "passed ponybot against revision
x'.

And we can get fancy, like check for test coverage in new code and
make sure it's covered. Or that some can post not a final patch, but a
link to git repository with a ticket branch, merge and do above (kinda
more future-resistant than patch).

Generalize it a bit, and it can perhaps be TracAwesomeBot everyone
could benefit from.

Cool for me, but have enough pet projects so now, but if anyone have
spare weekend to implement it? :) Or it could be GSoC '10 project.

Of course, only if it sounds cool for you, that is.

Almad
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

New to open source dev

[Joshua Russo]

I have been tinkering with some custom objects for db fields, form
fields, and widgets and have seen one or two things that might be nice
enhancements to the base objects. How exactly does the process of
contributing work?

I was actually coming here to gauge peoples opinion to my suggestions
but I'm not even sure if this is the proper place to ask if a mod is a
good idea or not.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

multiple lookups for date fields

[shadfc]

Hey everyone,
   I came across the need today to use something like
MyModel.objects.filter(date__month__gte=9).  However, that doesn't
work:
>>> ContactEvent.objects.filter(date__month__gte=9)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/share/djangos/django-trunk/django/db/models/
manager.py", line 129, in filter
return self.get_query_set().filter(*args, **kwargs)
  File "/usr/local/share/djangos/django-trunk/django/db/models/
query.py", line 466, in filter
return self._filter_or_exclude(False, *args, **kwargs)
  File "/usr/local/share/djangos/django-trunk/django/db/models/
query.py", line 484, in _filter_or_exclude
clone.query.add_q(Q(*args, **kwargs))
  File "/usr/local/share/djangos/django-trunk/django/db/models/sql/
query.py", line 1635, in add_q
can_reuse=used_aliases)
  File "/usr/local/share/djangos/django-trunk/django/db/models/sql/
query.py", line 1533, in add_filter
negate=negate, process_extras=process_extras)
  File "/usr/local/share/djangos/django-trunk/django/db/models/sql/
query.py", line 1843, in setup_joins
raise FieldError("Join on field %r not permitted. Did you misspell
%r for the lookup type?" % (name, names[pos + 1]))
FieldError: Join on field 'date' not permitted. Did you misspell
'month' for the lookup type?

I can achieve what I want using extra(), but I thought I'd ask how (im)
possible it would be to make my desired functionality work.   The SQL
(on postgres, at least) difference between filter(date__month=9) and
filter(date__month__gt=9) is a single character, but I realize that
has little do to with what it would take to get Django to do that.

thanks
Jay
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: multiple lookups for date fields

[Alex Gaynor]

On Tue, May 5, 2009 at 10:46 PM, shadfc  wrote:

>
> Hey everyone,
>   I came across the need today to use something like
> MyModel.objects.filter(date__month__gte=9).  However, that doesn't
> work:
> >>> ContactEvent.objects.filter(date__month__gte=9)
> Traceback (most recent call last):
>  File "", line 1, in 
>  File "/usr/local/share/djangos/django-trunk/django/db/models/
> manager.py", line 129, in filter
>return self.get_query_set().filter(*args, **kwargs)
>  File "/usr/local/share/djangos/django-trunk/django/db/models/
> query.py", line 466, in filter
>return self._filter_or_exclude(False, *args, **kwargs)
>  File "/usr/local/share/djangos/django-trunk/django/db/models/
> query.py", line 484, in _filter_or_exclude
>clone.query.add_q(Q(*args, **kwargs))
>  File "/usr/local/share/djangos/django-trunk/django/db/models/sql/
> query.py", line 1635, in add_q
>can_reuse=used_aliases)
>  File "/usr/local/share/djangos/django-trunk/django/db/models/sql/
> query.py", line 1533, in add_filter
>negate=negate, process_extras=process_extras)
>  File "/usr/local/share/djangos/django-trunk/django/db/models/sql/
> query.py", line 1843, in setup_joins
>raise FieldError("Join on field %r not permitted. Did you misspell
> %r for the lookup type?" % (name, names[pos + 1]))
> FieldError: Join on field 'date' not permitted. Did you misspell
> 'month' for the lookup type?
>
> I can achieve what I want using extra(), but I thought I'd ask how (im)
> possible it would be to make my desired functionality work.   The SQL
> (on postgres, at least) difference between filter(date__month=9) and
> filter(date__month__gt=9) is a single character, but I realize that
> has little do to with what it would take to get Django to do that.
>
> thanks
> Jay
> >
>
There's a ticket for this in django's trac:
http://code.djangoproject.com/ticket/10911

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: A Letter to the Authors of Web Authentication Libraries

[Paul Johnston]

Hi,

> If you want to get this into Django, I think you'll need to provide a solid
> proof of concept that shows you can work around the objections raised in
> this thread (graceful degradation, backwards compatibility) and, more
> importantly, that shows this is something actually useful and wanted.

Ok, fair comment. I do plan to add this to repoze.who, but no plans
for Django. The JavaScript library and instructions are there if you
guys want them, but that's it.

Thanks for the lively discussion,

Paul
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: DatabaseWrapper operators

[pbzRPA]

One more thing. Would you know if its mysql version related? I am
running 5.0.56 and am not sure if that might be the problem.

Thanks

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: DatabaseWrapper operators

[pbzRPA]

Hi,

Thanks for the advice, it has solved some of my problem but the "ś"
for example still does not get found when looking for "s".

But it's a step in the right direction. :)

Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Need Django Developer urgent

[Alex Gaynor]

On Tue, May 5, 2009 at 3:50 PM, Adi  wrote:

>
> Hello,
>
> I need Django Developer urgently.
>
> please email me back as soon as you can .
>
> thank you
>
> >
>
This is the wrong mailing list for a query of this nature, this should go to
django-users instead (and should probably contain more information).

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Need Django Developer urgent

[Adi]

Hello,

I need Django Developer urgently.

please email me back as soon as you can .

thank you

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: DatabaseWrapper operators

[Clément Nodet]

2009/5/5 pbzRPA 
>
> Hi, thank you for your input.
>
> The trouble I am having is that I have a polish database of users with
> polish letters in their names and surnames. Now not all international
> users have access to polish letters on their system therefore I need
> to be able to let a user enter English letters like "L" in there
> search and the search results should include all the polish names with
> "Ł" in them. This was why I was thinking of writing an operator that
> calls a function in the database to convert the letters on the run.
>

Hi,

Depending on the database engine you're using, it could be way easier
to rely on collations to solve your problem.

Check out this link ( http://bugs.mysql.com/bug.php?id=9604 ) if you're running
MySQL; regarding the 'Ł' and 'L' equality in polish and general unicode
collations. Seems like cp1250_general_* is the only one comparing all polish
characters 'correctly' to their english equivalent. Hope that helps,
--
Clément

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: DatabaseWrapper operators

[pbzRPA]

Hi, thank you for your input.

The trouble I am having is that I have a polish database of users with
polish letters in their names and surnames. Now not all international
users have access to polish letters on their system therefore I need
to be able to let a user enter English letters like "L" in there
search and the search results should include all the polish names with
"Ł" in them. This was why I was thinking of writing an operator that
calls a function in the database to convert the letters on the run.

Thanks.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---