Hi there,
I have a question on customize the db field. For this field, I want to
save integers in db, but want them to be my custom class when they are
used in Python code. In Django docs, it's said that I should set the
__metaclass__ to be models.SubfieldBase to make to_python() work. I
tried it
I'm new, so I don't know how to submit a patch. Our developers have
completed the extract_data function in django.db.models.related. It
seems to work fine.
extract_data:
"""
Pull out the data meant for inline objects of this class,
i.e. anything starting with our module
developers have free time for
it?
I'm just going to keep running with the patch locally, but I hate to
run software that's different that the trunk.
Thanks,
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi Jay,
>
> svk is your friend. It won't help with getting patches reviewed, but it
> does make keeping a tree of local patches almost painless. Here's my
> recipe:
>
> # set up mirrors of your
g ideas out of the air here. I have a lot more
experience in corporate environments than I do working with large
groups on an open source project, so I'm not sure how these issues are
usually handled.
Jay P.
--~--~-~--~~~---~--~~
You received this message becau
le". (As
well as levels of trust for long time contributers)
I guess this is just going to be a growing pain for Django, but one
I'm sure we're all willing to work through.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribe
aining
about dynamic typing or lack of interfaces, or some other design
choice they didn't understand.
Hopefully you can find a good median point where you can get your work
done without frustrating everyone here.
Jay P.
--~--~-~--~~~---~--~~
You received this messa
ing productive immediately, you
often lose out in the long term.
I'm not saying that Django shouldn't have some effort on that, after
all, it's the web framework for "perfectionists with deadlines", but
you have to beware of b
lade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966
>
> and maybe also
>
> http://www.encyclopediadramatica.com/index.php/Ilias
>
> ;)
Something seemed "off" the whole time with that guy, but he seemed to
be doing too
27;re updating a
row in the table, delete whatever the old file was"
Does anyone have any good API ideas for this? Am I the only one that
sees the use in it? I'd be willing to try writing the code, but I'd
appreciate some community feedback before getting started.
Thanks,
Jay P.
--~
On 6/14/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> Jay Parlar wrote:
> > So what I'm thinking, is to allow something like the following:
> >
> > class User(models.Model):
> > username = models.CharField(...)
> > avatar = model
ever get
called.
I'd submit a patch, but I have no idea what the proper solution is.
Am I missing something here? Is this just because I had a CharField as
a primary key?
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribe
On 6/16/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 6/16/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> > I just noticed today that if I have a CharField primary_key, with
> > 'blank=False', the system doesn't actually ever validate that the
&g
On 6/16/06, gabor <[EMAIL PROTECTED]> wrote:
>
> Jay Parlar wrote:
> currently you have to use manipulators, if you want to validate the data
> that enters your models, see
> http://www.djangoproject.com/documentation/forms/
>
> later, when validation-aware model
primary_key=True' from my CharField, a validation stage somewhere
caught it. I think the error message was "This field is required", or
something like that.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On 6/17/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> On 6/17/06, gabor <[EMAIL PROTECTED]> wrote:
> >
> > could you post your model and the relevant part of the view code?
> >
The relevant model:
class Product(models.Model):
product_name = models.Ch
o my article, with a pub_date of 2006-01-16 does NOT show up in the
results of the first query, but does in the second. Looks like the
comparison code somewhere is broken.
Note, I'm using sqlite3.
Jay P.
--~--~-~--~~~---~--~~
You received this message because y
ng.
>
> if you repeat this example in postgresql, it works.
>
> so it seems to be a bug with sqlite3... will dig around a little more.
>
It felt like a db error, because of *where* it was breaking, but I've
not yet looked into the ORM layer, and didn't have time to start
diggi
gt; Or more likely: http://softwaremaniacs.org/soft/tags/en/
I think Ian's own post about them is still the best initial resource:
http://feh.holsman.net/articles/2006/06/19/django-generic-relations
That contains a link to Jacob's tests for them, which illustrates very
nicely how to us
7;s a breakage I'm glad to deal with.
I'm consistently surprised when I try something like
Reporter.objects.filter(article=a) and it doesn't work. It seems so
much like it *should* work that I keep forgetting.
Jay P.
--~--~-~--~~~---~--~~
You received
methods to a variable, ie.
foo = SomeViewClass.GET
Unless you do a bunch of other things, you lose the function name in
the assignment.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&q
On 7/12/06, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> So I've got a model resembling:
>
> ==
> from django.contrib.auth.models import User
>
> class ExtendedUser(models.Model):
> user = models.OneToOneField(User)
>
> class Admin:
> list_display = ('user',)
> search
t (and some pertinent examples) are pretty concisely described on the
project's main page
(http://somethingaboutorange.com/mrl/projects/nose/)
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
was built for "archival"
purposes. I brought this up earlier in Django-users,
http://groups.google.com/group/django-users/browse_thread/thread/5b5d4fa5ad40f7bf/95de22e1e42b5d21
A thread you seem to have participated in :)
And no, I haven't had a chance to implement 'allow_future', or
a
>
> Any suggestions for how people would like to see this implemented?
Well, my initial thought (as I stated in the previous thread) was an
'allow_future' keyword that defaults to False. That way it's backwards
compatible.
Jay P.
--~--~-~--~~~--
I just added a patch (http://code.djangoproject.com/ticket/2466) that
adds a 'filesize' filter, which returns filesizes (from get_XXX_size)
in a human friendly way.
It's trivially simple, but I thought it might be useful to
Oh jeez, I just noticed the 'filesizeformat' filter...
Well, there's 5 minutes of my life I'll never get back :)
Jay P.
On 8/1/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> I just added a patch (http://code.djangoproject.com/ticket/2466) that
> adds a 'file
I'm in general a big fan of setuptools. However, I don't really see a
need for it in Django.
I say dump it.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
ere is an effort to move to entry points, then yeah, keep
setuptools. Otherwise though...
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
ools eventually when dealing with Python.
"python setup.py install" has been the defacto standard for years and
years, it's a distutils feature.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
'TESTING' from 'settings', unless you want to do a 'from settings
import TESTING'.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
; will have *extra* functionality -- namely, that people will be able to
> fall into SQLAlchemy syntax if they want to.
>
A question then: Once the SQLAlchemy stuff is in and solid, will there
be any reason *not* to use it?
Jay P.
--~--~-~--~~~---~--~~
You recei
pointing that out.
The reason you've never used it before (and couldn't find it) is
because it's new in Python 2.5, which hasn't even hit its official
release yet :)
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscri
th/models.py
in create_row_level_permission, line 58
Is there a problem with my understanding of things here? Is there a
reason that RowLevelPermissions shouldn't be allowed on models with a
OneToOne? I can see the technical reason in the code, namely that the
code a
ows = False
class Meta:
row_level_permissions = True
I have a user "q2" with the general permissions "Can add role" and
"Can delete role".
I log into the Admin with "q2", and add a new row. Works fine. Go back
to the main admin page, and
On 9/12/06, Chris Long <[EMAIL PROTECTED]> wrote:
>
> I'll take a look at it today.
>
> Chris
>
Thanks. Let me know if you need any more details on anything, I'll be
around most of the day.
Jay P.
--~--~-~--~~~---~--~~
You receiv
and see if it fixes this problem.
Looks to be working now, thanks a lot.
Jay P.
--~--~-~--~~~---~--~~
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@go
lse happens.
My entire site right now is run by generic views, so all my needs come
in at the Admin level. I have about 10 people who are allowed to log
into the Admin, and I basically don't want them to edit each others'
UserProfile and Articles.
So
bj_instance._get_pk_val()
+all_data = {'owner_id':owner.id,
'model_ct_id':self.ct.id, 'model_id':model_id,
'permission_id':perm.id}.py
manipulators.manipulator_validator_unique_to
ttributeError at
/admin/members/userprofile/5/row_level_permissions/delete/40/4/1f7b5231f975bbf52bb0298181987ea43fbc75cb/
'UserProfile' object has no attribute 'id'
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subsc
I'm going to keep lobbing them at you, until it all works :)
I'm still trying to delete a row level permission, and I'm getting:
Traceback (most recent call last):
File
"/Users/jayparlar/Library/Python2.4/site-packages/django/core/handlers/base.py"
in get_response
74. response = callback(requ
Oh, and interestingly, the row level permission I was trying to delete
*does* in fact get deleted, despite my seeing this error.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
-One though, 'user_id' is
returned, instead of 'id' like all the other related objects.
If I hardcode it to be 'id' instead of m2m_reverse_name(), then
everything works, but that's obviously not the right solution.
Jay p.
--~--~-~--~~---
id, 'model_id':model_id,
'permission_id':perm.id}.py
manipulators.manipulator_validator_unique_together(field_name_list,
self.opts, self, field_data, all_data)
utils.pyc
rlp =
RowLevelPermission.objects.create_row_leve
; Let me know how it goes.
Worked perfectly! I'll let you know if anything else comes up.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, s
hen everything works
fine and dandy.
Any thoughts, Chris?
(And I've tried dropping and recreating the auth_rowlevelpermission db
table, to no avail).
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dj
have to revisit it
> soon.
>
Alright, the fix worked for me.
For my current uses, the RLP branch is now working exactly how I want it to!
Are any other people doing much testing with the branch? It'd be nice
to see it get moved to the trunk, but I know that won't happen withou
a evolution, multi-db, multi-auth and
search-api branches. I think it'd be great to get all of those into
the Django core/contrib, but without more testing of them, it'll never
happen.
Just my two cents.
Jay P.
--~--~-~--~~~---~--~~
You received this m
On 9/20/06, Nick <[EMAIL PROTECTED]> wrote:
>
> Jay Parlar wrote:
>
> > There's still the schema evolution, multi-db, multi-auth and
> > search-api branches. I think it'd be great to get all of those into
> > the Django core/contrib, but without m
(Chris),
After a recent update of the row-level branch, every single instance
of every model in the Admin is now getting the "Edit Row Level
Permissions" button on the top right, even the models that don't have
"row_level_permissions = True" in
und in my testing.
It looks like it's also been the most active branch, at least
recently. Although I *seem* to remember Jason Pellerin being pretty
confident with the state of the multi-db branch, within his own use
cases.
Jay P.
--~--~-~--~~~---~--~~
You recei
eem to be any bugs
in it within my use cases.
Jay P.
--~--~-~--~~~---~--~~
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 u
talling it using "python setup.py install".
Python 2.5 with OS X 10.4.8 (Intel) seems fine. I'll try Python 2.4
with OS X 10.3.9 when I get home.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
OS X 10.3.9 with Python 2.4.3 seems fine.
Jay P.
--~--~-~--~~~---~--~~
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 u
nd post the URL. I
know I'd certainly have use cases for it, even if it doesn't make it
into the Django core.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
I think that Tom Tobin ([EMAIL PROTECTED]) was given the job of
administering the Trac whitelist.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
pretty minimal, but it's working so far for
what I'm doing.
Jay P.
--~--~-~--~~~---~--~~
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@g
tell people all the time that it's generally safe to run
Django off the trunk, but if a bunch of untested branches are merged
in, well, welcome to disaster time.
I wasn't around during the magic removal merging, but I'd assume that
a lot of people were involved, testing out changes.
testing on it, found a few bugs, and they were
all fixed by the maintainer. I would guess that it is the branch
that's closest to being ready (if not ready already, which it is for
my use cases, I'm running this branch in production)
Jay P.
--~--~-~--~~~--
remember an interview with him saying that he was using the
Django template language, but that was just about it.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
and Content has a FK to
> ContentType. This is where I tell it if the content is text or other
> media content.
Django has a builtin type called "ContentType",
http://code.djangoproject.com/browser/django/trunk/django/contrib/contentty
share my model offline if
> needed.
ContentType is used all over the place, if I remember correctly (been
awhile since I looked). Marc is right, it's a reserved name. It's a
bit like saying you want to use the word "if" as a variable name. It's
reserved, it has it's pl
> http://code.djangoproject.com/wiki/ProfilingDjango
Maybe this is what you're looking for? http://zilbo.com/@perfmon It's
Ian Holsman's Django performance monitor. He used to be *very* active
in the Django community. Don't know whether or no
e persuaded to
take it over as a SoC project, being the PhD student that I am.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
being used for real-world, useful things
(Washington Post, all the Lawrence stuff, etc.). The development of
Django is not an academic exercise, it's being done to facilitate
solutions to real-world problems.
Jay P.
--~--~-~--~~~---~--~~
You received this me
people move their installs to 0.96.
[1] :
http://groups.google.com/group/django-users/browse_thread/thread/4340284e3b4705ba
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" grou
On 4/11/07, Simon G. <[EMAIL PROTECTED]> wrote:
>
> Hi Jay,
>
> Someone reported that issue a few weeks ago, and I added a quick patch
> for this here:
>
> http://code.djangoproject.com/ticket/3830
>
> It can probably be enhanced beyond that though.
D'oh,
I guess it all just depends on your measure of "success".
Jay P.
--~--~-~--~~~---~--~~
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@googleg
environ[str("REQUEST_URI")] = self.path
+return environ
We have been using a branch with this change applied to 1.11 in both
development and production since the PR was submitted, though the related
WSGI middleware is not yet in production.
Thanks for
ave a page that gives a short summary of
each contrib app
(http://www.djangoproject.com/documentation/add_ons/), so people
interested in using contrib apps will know what it does anyway.
+1 for django.contrib.bikeshed
Jay P.
--~--~-~--~~~---~--~~
You received this
tions aren't going to change
too often, so the db's cache (if any) should return the result quick
enough, and you know that in *all* circumstances, a db will be
present.
Of course, that's just my opinion for the colour of this particular bikeshed.
Jay P.
--~--~-~--~~--
hanks
...
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 [EMAIL
rib. I would personally rather have
an S3FileField.
Of course, if you changed FileFIeld such that you could use it with
*any* S3-style provider, by passing it the right data (maybe some
callbacks, or something), that'd be cool.
Jay P.
--~--~-~--~~~---~--~~
You
o
restrict dynamic behaviours. It is simply an optimization technique.
It is generally considered "wrong" to use __slots__ for restrictive
purposes, as it goes against the grain of Python.
And I'm not sure if you've actually run that code, or if I'm missing
something, but
y, hard-to-fathom side effects
that should only be used by programmers at grandmaster and wizard
levels. Unfortunately it has gained an enormous undeserved popularity
amongst the novices and apprentices, who should know better than to
use this magic incantation
y
to help. Haven't really posted in 6 months or so, as I'm not currently
working on any Django projects, but I do read the lists every day.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dja
isated over
and over again.
I understand wanting to handle the case where some data has changed,
but shouldn't there be some sort of cache so we don't need to keep
recreating the instances?
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are
I'm essentially wondering whether we can do the reverse of what's
being done now. You currently instantiate the form, and do a
security_hash on it. I'd like to do a hash on the POST data, and then
instantiate if necessary (i.e. if we haven't already instanti
On 4/11/08, Honza Král <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 11, 2008 at 4:15 PM, Jay Parlar <[EMAIL PROTECTED]> wrote:
> > Currently when we call get_form(i, request.POST) in __call__, we just
> > arbitrarily recreate the Form instance. What if on the firs
hat alteration to globally affect
all users. Because this chunk of text is listed in the process_step()
documentation, I got the impression that form_list was much more
fine-grained than that.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are su
I realize that you can do it with initial. I was asking (unclearly,
evidently) if there would be any value to changing django to work in
that way.
Jay
[EMAIL PROTECTED] wrote:
> This question should be directed to django-users, this group is for
> django development, not s
Hello everyone.
Myself , Jay Dev Jha, from Indian Institute Of Information Technology
Imphal, want to contribute to this organization.
I am currently working on designing my own website using django.
The registratison app is not compatible with older version of django when
it automatically
82 matches
Mail list logo
