Re: please help

[ABHINAV MISRA]

Thank you Sir
Now I shall get started with the project.

Regards
Abhinav Misra

On Monday, 28 January 2013 18:47:53 UTC+5:30, ABHINAV MISRA wrote:
>
> I am Abhinav Misra, an undergraduate.
> I was going through the project ideas of GSoC 2012 so as to find any 
> project of which I am capable of.
> There i came up with the project named: " improved error reporting  ". I 
> want to take this project as my GSoC 2013 project.
> Till now GSoC 2013 is not announced but even if it is not happening I 
> would like to take it as a project for my summers this year .
> I am not sure whether the project is completed till yet or not ?
>
> I know python and C and I am currently learning java. I use eclipse and 
> also netbeans as my IDE. I am well versed with git.
> Please guide me as to how can i approach this project and what should i do 
> to successfully complete this project 
>
> thanking you.
>
> regards
> Abhinav Misra
>

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

Re: Possible ORM bug with SQL syntax & generic relations

[Ian Kelly]

On Wed, Jan 30, 2013 at 10:10 PM, Dylan Klomparens
 wrote:
> It's interesting this seems to work with 10g XE. I am not sure if this is
> relevant, but I am using the Full Oracle Client with Administrative Tools
> (as oppose to the Oracle Instant Client) and cx_Oracle for Python access to
> the database. The error I felt was most problematic is that the SQL
> statement has 4 opening parenthesis, and only 3 closing parenthesis. This
> kind of statement work in Oracle 10g XE?

I noticed that also, but I thought that perhaps it was a transcription
error, since you said it works with sqlite3.  The Oracle version
should not make any difference for this query.  More likely I just
didn't hit the same query.  What version of Django are you using?
Also it might help if you posted your ModelAdmin, in case that's
affecting the query.  My test used a default ModelAdmin.

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

Re: Form.set_data method

[Wim Feijen]

Interestingly enough, it reminds me of the pattern proposed by Daniel 
Greenfeld and Miguel Araujo, who used a pattern:

form = MyForm(request.POST or None)

http://blip.tv/djangocon/advanced-django-form-usage-5573287

Wim

On Thursday, 31 January 2013 07:08:52 UTC+1, Shai Berger wrote:
>
> On Thursday 31 January 2013, Byron Ruth wrote: 
> > Here is the ticket: https://code.djangoproject.com/ticket/19668 and the 
> > pull request https://github.com/django/django/pull/674 
> > 
> > One user commented on the ticket raising a concern that it could 
> possibly 
> > be misused if the data is set after it had been used. It is certainly a 
> > valid concern, however it should be made clear in the docs when to use 
> it 
> > and/or raise an exception if `is_valid` has already been called. 
> > 
> > Thoughts? 
>
> While this is backwards-compatible per se, using it in views is generally 
> not 
> backwards-compatible with user form classes (you can't tell what they do 
> in 
> their initializers); thus, generic views (and also some not-generic views) 
> are 
> forced to keep using the "old way" unless the (user) form code is altered. 
> Which means, you'll have two ways to do the same thing (in views), without 
> a 
> clear preference between them. 
>
> So if you want this judged as a backwards-compatible change, I'm -1. 
>
> As a non-backwards-compatible change, I'd like it, but I don't think it's 
> worth the disruption, so I'm -0. 
>
> Either way, I'm not a core dev. 
>
> Shai. 
>
>

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

Re: Form.set_data method

[Shai Berger]

On Thursday 31 January 2013, Byron Ruth wrote:
> Here is the ticket: https://code.djangoproject.com/ticket/19668 and the
> pull request https://github.com/django/django/pull/674
> 
> One user commented on the ticket raising a concern that it could possibly
> be misused if the data is set after it had been used. It is certainly a
> valid concern, however it should be made clear in the docs when to use it
> and/or raise an exception if `is_valid` has already been called.
> 
> Thoughts?

While this is backwards-compatible per se, using it in views is generally not 
backwards-compatible with user form classes (you can't tell what they do in 
their initializers); thus, generic views (and also some not-generic views) are 
forced to keep using the "old way" unless the (user) form code is altered. 
Which means, you'll have two ways to do the same thing (in views), without a 
clear preference between them.

So if you want this judged as a backwards-compatible change, I'm -1.

As a non-backwards-compatible change, I'd like it, but I don't think it's 
worth the disruption, so I'm -0.

Either way, I'm not a core dev.

Shai.

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

Re: Possible ORM bug with SQL syntax & generic relations

[Dylan Klomparens]

It's interesting this seems to work with 10g XE. I am not sure if this is
relevant, but I am using the Full Oracle Client with Administrative Tools
(as oppose to the Oracle Instant Client) and cx_Oracle for Python access to
the database. The error I felt was most problematic is that the SQL
statement has 4 opening parenthesis, and only 3 closing parenthesis. This
kind of statement work in Oracle 10g XE?


On Wed, Jan 30, 2013 at 7:30 PM, Ian Kelly  wrote:

> On Wed, Jan 30, 2013 at 4:30 PM, Dylan Klomparens
>  wrote:
> > Hello,
> >
> > I've encountered what may be a Django ORM bug and am writing to see what
> the
> > dev community thinks. I have a model that uses generic relations. An
> error
> > is returned when I attempt to delete multiple rows of said model in the
> > database table. The error is repeatable, and I have found it is only
> > applicable to models that contain generic relations. The error occurs
> after
> > the deletion is confirmed in the admin interface and the SQL statement
> > begins execution.
> >
> > I've attached the use case that creates the bug, the generated SQL
> statement
> > (read from the debug output), and the model in question.
> >
> > Could someone please confirm that this is indeed a bug? If so, I can
> create
> > a ticket and begin researching how to remedy this problem.
>
> I can confirm that the attached SQL is problematic for Oracle.  It has
> an ORDER BY clause inside an IN subquery, which is meaningless in
> general and not permitted by Oracle.  However, I was not able to
> confirm the bug using Django 1.5rc1 and Oracle 10g XE.  I tried
> replicating the case with the model provided, and the multiple
> deletion was successful.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Form.set_data method

[Byron Ruth]

Here is the ticket: https://code.djangoproject.com/ticket/19668 and the 
pull request https://github.com/django/django/pull/674

One user commented on the ticket raising a concern that it could possibly 
be misused if the data is set after it had been used. It is certainly a 
valid concern, however it should be made clear in the docs when to use it 
and/or raise an exception if `is_valid` has already been called.

Thoughts?

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

Re: Tutorial review

[Daniele Procida]

On Thu, Jan 31, 2013, Daniele Procida  wrote:

>There has been some discussion of the tutorials on IRC, and at the same
>time I've been working through the tutorials again.
>
>I've made some amendments (who knows, they may even amount to
>improvements) and commented on them, at django/pull/688/files>.
>
>Some of the changes are just expanations, but some affect the tutorial code.
>
>Ticket: .
 
Or even .

Daniele

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

Tutorial review

[Daniele Procida]

There has been some discussion of the tutorials on IRC, and at the same time 
I've been working through the tutorials again.

I've made some amendments (who knows, they may even amount to improvements) and 
commented on them, at .

Some of the changes are just expanations, but some affect the tutorial code.

Ticket: .

Daniele

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

Re: Possible ORM bug with SQL syntax & generic relations

[Ian Kelly]

On Wed, Jan 30, 2013 at 4:30 PM, Dylan Klomparens
 wrote:
> Hello,
>
> I've encountered what may be a Django ORM bug and am writing to see what the
> dev community thinks. I have a model that uses generic relations. An error
> is returned when I attempt to delete multiple rows of said model in the
> database table. The error is repeatable, and I have found it is only
> applicable to models that contain generic relations. The error occurs after
> the deletion is confirmed in the admin interface and the SQL statement
> begins execution.
>
> I've attached the use case that creates the bug, the generated SQL statement
> (read from the debug output), and the model in question.
>
> Could someone please confirm that this is indeed a bug? If so, I can create
> a ticket and begin researching how to remedy this problem.

I can confirm that the attached SQL is problematic for Oracle.  It has
an ORDER BY clause inside an IN subquery, which is meaningless in
general and not permitted by Oracle.  However, I was not able to
confirm the bug using Django 1.5rc1 and Oracle 10g XE.  I tried
replicating the case with the model provided, and the multiple
deletion was successful.

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

Re: Python/Django developer job opportunity

[Russell Keith-Magee]

Please don't post job advertisements to django-developers. Django-dev is a
list for discussing the development of Django itself.

If you want to post job advertisements, you're welcome to do so on
Django-users.

Yours,
Russ Magee %-)

On Thu, Jan 31, 2013 at 4:27 AM,  wrote:

> We are looking for a Full Stack Software Engineer with strong Python,
> Django, and JavaScript skills, some C++.
>
> Our client is a startup company founded in 2009 by a group of MIT
> engineers. They are supported by investors responsible for world-class
> companies. They are looking for talented developers for join their amazing
> team and work on various projects of interest, from their unique user
> interfaces to their custom-designed hardware systems.
>
> *Responsibilities:*
>
> Create software to connect disparate software systems. Architect and
> develop new features for custom tablet hardware. Ensure backend webservices
> efficiently process and analyze large amounts of incoming data. Develop
> general interfaces and tools to make our development, operations, and sales
> teams more efficient. Design systems to augment existing software, enabling
> it to transmit data and concepts not part of the original product.
> Communicate directly with 3rd party vendors to determine how best to
> integrate with their systems.
>
> *Skill requirements:*
>
> Strong skills in Python, Django, JavaScript, and some C++. Excellent
> communication skills both in-person & via text-only means. Experience in
> cross-platform development, XML/REST/COM interfaces, machine learning,
> network protocols, data mining and working with undocumented APIs are a
> major plus.
>
> *Contact Note :*http://renttesters.com/careers/apply/12131/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Re: Possible ORM bug with SQL syntax & generic relations

[Dylan Klomparens]

Something I forgot to mention: I have *only observed the bug using Oracle
11g*. Everything seems to work fine with SQLite3.


On Wed, Jan 30, 2013 at 6:30 PM, Dylan Klomparens <
dylan.klompar...@gmail.com> wrote:

> Hello,
>
> I've encountered what may be a Django ORM bug and am writing to see what
> the dev community thinks. I have a model that uses generic 
> relations.
> An error is returned when I attempt to delete multiple rows of said model
> in the database table. The error is repeatable, and I have found it is only
> applicable to models that contain generic relations. The error occurs after
> the deletion is confirmed in the admin interface and the SQL statement
> begins execution.
>
> I've attached the use case that creates the bug, the generated SQL
> statement (read from the debug output), and the model in question.
>
> Could someone please confirm that this is indeed a bug? If so, I can
> create a ticket and begin researching how to remedy this problem.
>
> -- Dylan
>

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

Possible ORM bug with SQL syntax & generic relations

[Dylan Klomparens]

Hello,

I've encountered what may be a Django ORM bug and am writing to see what
the dev community thinks. I have a model that uses generic
relations.
An error is returned when I attempt to delete multiple rows of said model
in the database table. The error is repeatable, and I have found it is only
applicable to models that contain generic relations. The error occurs after
the deletion is confirmed in the admin interface and the SQL statement
begins execution.

I've attached the use case that creates the bug, the generated SQL
statement (read from the debug output), and the model in question.

Could someone please confirm that this is indeed a bug? If so, I can create
a ticket and begin researching how to remedy this problem.

-- Dylan

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


DELETE FROM "NANOFAB_ACTIVITYHISTORY" WHERE "ID" IN (SELECT 
"NANOFAB_ACTIVITYHISTORY"."ID" FROM "NANOFAB_ACTIVITYHISTORY" INNER JOIN 
"DJANGO_CONTENT_TYPE" ON ("NANOFAB_ACTIVITYHISTORY"."CONTENT_TYPE_ID" = 
"DJANGO_CONTENT_TYPE"."ID") INNER JOIN "NANOFAB_USER" ON 
("NANOFAB_ACTIVITYHISTORY"."AUTHORIZER_ID" = "NANOFAB_USER"."ID") WHERE 
"NANOFAB_ACTIVITYHISTORY"."ID" IN (:arg0, :arg1) ORDER BY 
"NANOFAB_ACTIVITYHISTORY"."DATE" DESC

Note, the bindings in this statement are :arg0 = 3 and :arg = 2<>class ActivityHistory(models.Model):
"""
Stores the history of when accounts, projects, and users are active.
This class uses generic relations in order to point to any model type.
For more information see: 
https://docs.djangoproject.com/en/dev/ref/contrib/contenttypes/#generic-relations
"""

class Action:
ACTIVATED = True
DEACTIVATED = False
Choices = (
(ACTIVATED, 'Activated'),
(DEACTIVATED, 'Deactivated'),
)

content_type = models.ForeignKey(ContentType)
object_id = models.PositiveIntegerField()
content_object = generic.GenericForeignKey('content_type', 'object_id')
action = models.BooleanField(choices=Action.Choices, help_text="The 
target state (activated or deactivated).")
date = models.DateTimeField(default=timezone.now, help_text="The time 
at which the active state was changed.")
authorizer = models.ForeignKey(User, help_text="The staff member who 
changed the active state of the account, project, or user in question.")
class Meta:
ordering = ['-date']
verbose_name_plural = 'activity histories'
def __unicode__(self):
if self.action:
state = "activated"
else:
state = "deactivated"
return unicode(self.content_type).capitalize() + " " + 
unicode(self.object_id) + " " + state

Python/Django developer job opportunity

[gazarova78]

We are looking for a Full Stack Software Engineer with strong Python, 
Django, and JavaScript skills, some C++.

Our client is a startup company founded in 2009 by a group of MIT 
engineers. They are supported by investors responsible for world-class 
companies. They are looking for talented developers for join their amazing 
team and work on various projects of interest, from their unique user 
interfaces to their custom-designed hardware systems.

*Responsibilities:*

Create software to connect disparate software systems. Architect and 
develop new features for custom tablet hardware. Ensure backend webservices 
efficiently process and analyze large amounts of incoming data. Develop 
general interfaces and tools to make our development, operations, and sales 
teams more efficient. Design systems to augment existing software, enabling 
it to transmit data and concepts not part of the original product. 
Communicate directly with 3rd party vendors to determine how best to 
integrate with their systems.

*Skill requirements:*

Strong skills in Python, Django, JavaScript, and some C++. Excellent 
communication skills both in-person & via text-only means. Experience in 
cross-platform development, XML/REST/COM interfaces, machine learning, 
network protocols, data mining and working with undocumented APIs are a 
major plus.

*Contact Note :*http://renttesters.com/careers/apply/12131/

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