Just wondering what the procedure is for getting a patch accepted? I
submitted a patch (http://code.djangoproject.com/ticket/1994) a week
ago, and have had no feedback on it so far.
Is there some kind of monthly IRC meetup where pending patches are
discussed? Or is it just when the core developer
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 repository and django trunk
> # and copy dj
On 5/31/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> It's the latter. Me, I generally have one afternoon a week in which I
> focus on clearing out patches and tickets, plus weeknights as my
> schedule allows. I'm pretty sure Jacob works the same way, although he
> has been *super* busy traveli
On 5/31/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Could you trust a patch when some other developers have positively
> reviewed it? This might take a time until your ideas of proper patches
> have been "revealed", but then we'd have a more or less peer review
> system. And it could get the
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Additionally: The fact that I have _not_ the full domain knowledge (=
> background information) enables me to make those "sweeping suggestions"
> from a newcomers point of view (who cares not much about project details
> and internals, but j
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> And an efficient tool should assist a user to become productive immediately.
>
> http://case.lazaridis.com/multi/wiki/Product#Functionality
>
> There are webframeworks which provide this functionality.
>
What exactly are you basing that c
On 6/2/06, Carlo C8E Miron <[EMAIL PROTECTED]> wrote:
>
> On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote:
> >
> > I would advise all respected Django contributors to follow the path
> > mentioned here:
> >
> > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/138966
>
> an
So I've been thinking a lot recently about FileField/UploadField, and
how restricting they are for any app that might want users to upload
files.
Namely, the fact that the upload_to can only use strftime() to vary
the directories.
I did submit a patch (http://code.djangoproject.com/ticket/1994)
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
I just noticed today that if I have a CharField primary_key, with
'blank=False', the system doesn't actually ever validate that the
field isn't empty.
I tracked down the check to the method 'validate_full' which lives in
db/models/fields/__init__.py
It seems to me that this function is never bei
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
On 6/17/06, gabor <[EMAIL PROTECTED]> wrote:
>
> could you post your model and the relevant part of the view code?
>
I can't today, it'll have to wait until Monday. I'll make sure to
throw it up then.
An interesting thing though, is that when I removed the
'primary_key=True' from my CharField, a
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
I posted this on django-users, but didn't get much feedback. It seems
like a pretty important problem, so I'm reposting here:
My current model looks like this:
class Article(models.Model):
title = models.CharField(maxlength=64)
slug = models.SlugField(prepopulate_from=("title",))
autho
On 6/19/06, gabor <[EMAIL PROTECTED]> wrote:
>
>
> that seems to be the problem.
> it works with postgresql.
>
> if you want to verify the problem:
>
> import django.db
> print django.db.connection.queries
>
> this will print out the sql queries django is doing.
>
> in this case it does something
On 6/23/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> I somewhat missed the whole discussion on generic relation though I get
> the general idea. Do they work for ManyToMany relations? And is there
> any description of how to use them?
>
> > but it has a very neat Tag widget for the Admin.
>
>
On 6/30/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> However, since this change could effect people in the field, I thought I'd
> check for objections before I commit.
>
> Comments?
I think that personally it will break one or two things for me, but
it's a breakage I'm glad to deal wi
On 7/4/06, Ryan Mack <[EMAIL PROTECTED]> wrote:
> Here's my issue: Is simply requiring that these method names be uppercase
> enough to distinguish them from non-http method handling methods? I've
> created an httpmethod decorator to help further distinguish these methods,
> but at times it fee
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
On 7/12/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> Unless you can make a particularly convincing case for using an alternative,
> based upon some deficiency of unittest that will adversely affect django
> testing, I'm inclined to stick with whats in the standard library.
>
> If the powe
On 7/26/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> Hi.
>
> I was wondering what the rationale is behind having the date-based generic
> views only show 'historical' events.
> they all seem to have
> # Only bother to check current date if the date isn't in the past.
> if date >= now.dat
On 7/26/06, Tyson Tate <[EMAIL PROTECTED]> wrote:
> I'm +50 on this because I'm about ready to jump in to a large calendar
> project next week and I'll need this functionality. If no one beats me
> to it, I'll try to remember to hammer out a patch next week.
>
> Any suggestions for how people wou
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 others.
Jay P.
--~--~-~--~~~---~--~~
Y
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.
To post to this group, s
On 8/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Here are a couple that I've been thinking about, both using setuptools
> entry points.
Hmm... I forgot about that. Jason's right, entry points do rule. At
least from what I've seen of them in nose.py :)
If there is an effort to move to e
On 8/2/06, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>
> > Adrian Holovaty wrote:
> > >
> > > So, convince us to continue using setuptools. What incentive do we
>
> The easy packaging is a big plus, and I think, too, that "python
> setup.py install" is becoming somewhat of the defacto python
> insta
On 8/29/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> Personally, I find myself leaning towards option 3 - outside of testing, I
> can't see any use case for a template-rendering signal, and I don't like
> special cases. Instrumentation of the rendering system as part of the test
> framewor
On 8/30/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> The goal is that this will have *zero* effect on existing queries. The
> Django query syntax will remain exactly the same, and the database API
> will stay the same. The only difference is that the SQLAlchemy backend
> will have *extra* func
On 9/7/06, Nate Straz <[EMAIL PROTECTED]> wrote:
> Wow, I never knew about that syntax. I checked the Language Reference
> all the way back to the 1.5 release and it is in every release. I'm
> surprised I've never seen that syntax used before.
>
> Thank you for pointing that out.
The reason yo
I decided to try out the RowLevelPermissions branch today, and apply
it to some code I haven't put into production yet.
My model is essentially this:
class UserProfile(models.Model):
home_address = models.TextField(blank=True,null=True)
user = models.OneToOneField(User)
class Admin:
More playing with the per-object branch, and just received this error:
Traceback (most recent call last):
File
"/Users/jayparlar/Library/Python2.4/site-packages/django/core/handlers/base.py"
in get_response
74. response = callback(request, *callback_args, **callback_kwargs)
File
"/Users/jaypa
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 received this message because you are su
On 9/12/06, Chris Long <[EMAIL PROTECTED]> wrote:
>
> Nope, not a correct assumption.
>
> Fixed in the latest version, I did try it with the model you have given
> and it does work, but the test was not as indepth (lack of time this
> week). So please give it a try and see if it fixes this problem
On 9/12/06, Chris Long <[EMAIL PROTECTED]> wrote:
>
> Latest changeset should fix it.
>
> Chris
Worked like a charm!
I've got pretty minimal needs right now, when it comes to the
row-level permissions, but I'll keep working with it and let you know
if anything else happens.
My entire site right
Another problem along the same vein just popped up.
I was trying to add a "change user profile" row level permission for a
user, and I got this:
Traceback (most recent call last):
File
"/Users/jayparlar/Library/Python2.4/site-packages/django/core/handlers/base.py"
in get_response
74. response
And another one. This time I'm trying to delete a row level
permission. Not sure what the correct fix for this one is.
Traceback (most recent call last):
File
"/Users/jayparlar/Library/Python2.4/site-packages/django/core/handlers/base.py"
in get_response
74. response = callback(request, *call
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" group.
To p
The error seems to be related to this code in db/models/query.py:
for related in cls._meta.get_all_related_many_to_many_objects():
for offset in range(0, len(pk_list), GET_ITERATOR_CHUNK_SIZE):
cursor.execute("DELETE FROM %s WHERE %s IN (%s)" % \
Great. Also, don't forget about the patch from a few messages ago, namely:
--- django/contrib/admin/row_level_perm_manipulator.py (revision 3753)
+++ django/contrib/admin/row_level_perm_manipulator.py (working copy)
@@ -77,7 +77,8 @@
#Check that the new row level perms are unique
On 9/17/06, Chris Long <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> Latest release should fix both. The user_id problem is related to the
> generic relations used in the POP branch, I've written up a ticket
> #2749 about it, but it has been fixed in my branch.
>
> Let me know how it goes.
Worked perf
Having a problem right now when settings show_all_rows to False in a
model with OneToOne. Basic model is this (same as my other posts on
OneToOne and RLP):
class UserProfile(models.Model):
home_address = models.TextField(blank=True,null=True)
user = models.OneToOneField(User)
class
On 9/18/06, Chris Long <[EMAIL PROTECTED]> wrote:
>
> The problem appears to be related to the same stuff we've been dealing
> w/ earlier. This line(django.contrib.admin.main.ChangeList line 695):
>
> qs =
> self.manager.filter(id__in=RowLevelPermission.objects.get_model_list(self.user
On 9/18/06, Nick <[EMAIL PROTECTED]> wrote:
>
> Most, if not all, of the "little, easy improvements" listed on
> www.djangoproject.com have now been made. I feel the urge on
> contribute once more, so is there anything else little and easy that I
> could do?
>
My suggestion would be to help do s
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 their Meta class.
Jay P.
--~--~-~--~~-
On 10/14/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Hey there,
>
> I'm very interested in getting this done, but we've got quite a few
> branches open at the moment. I think we should focus on merging at
> least one of these branches before opening another one, for the sake
> of everybody's
On 10/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Actually I have a need for both row-level-permissions (at least I
> hope the model fits my needs) AND multi-db branch so would be thrilled
> to be able to easily get them both.
>
Well, all I can say about that is try testing with t
On 10/16/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> But I have only tested this on Linux, so I'd appreciate it if folks
> could test out the command "python setup.py install" on various
> different platforms. Just grab the SVN version of Django and try
> installing it using "python setup.py
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 unsubscribe from
On 10/27/06, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> I'd like to add a Middleware class that I wrote to the Wiki, but I keep
> getting rejected by askimet.
>
> The class requires an authenticated user for every view. This is
> beneficial for any closed project. Does anyone suppose something lik
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, send email t
I've reported at least a few times on django-dev and django-users that
I've had a lot of success with row-level-permissions. I found some
bugs early on, but Chris Long squashed them all for me. I'm currently
running a production site with that branch.
My requirements of it are pretty minimal, but
On 11/6/06, David Blewett <[EMAIL PROTECTED]> wrote:
>
> I would like to suggest that the branches that are felt to be complete
> sans testing be merged into a single branch. I am anxiously awaiting
> several different branch merges to core but do not have time to check
> each individual one out t
On 11/7/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Another proposal:
>
> Let's have a branch of the month, announced on devel and users. The
> branch is then frozen, merged with trunk, and will be merged at a fixed
> date into trunk if no critical and unfixable bugs are found. This would
> e
On 12/1/06, James <[EMAIL PROTECTED]> wrote:
>
> I'd read somewhere that he expresses a preference for Django, but seems
> he's using it for real work:
>
> "Guido van Rossum, author of the Python programming language, has begun
> showing off his first project since joining Google last year ... The
On 1/30/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> I'm getting a weird bug here and this is what I've deduced...
>
> I've got a "Page" model and a "Content" model. Content has a FK to
> Page. I also have a "ContentType" model and Content has a FK to
> ContentType. This is where I tell it if
On 1/31/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
>
> > Django has a builtin type called "ContentType",
> > http://code.djangoproject.com/browser/django/trunk/django/contrib/con...
> >
> > I'd just rename yours to something else and be done with it.
>
> As a workaround, sure. I've already worked
On 2/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I'd like to do some code profiling of my application/projects, and I'm
> confused about how to go about it. I found a wiki entry that
> references hotshot, but I'm not sure where to go from here.
>
> http://code.djangoproject.com/wiki/Pro
On 2/26/07, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
> I for one am very keen to see RLP branch integrated and I tested it
> months ago to my satisfaction.
>
> [1]
> http://groups.google.com/group/django-developers/browse_thread/thread/f124083c6194dccc/
I too would be very excited to see it
On 4/7/07, Noah <[EMAIL PROTECTED]> wrote:
>
> I'm worried about a trend I've seen before in other frameworks etc.
> They start off easier to use and over time get more and more
> generalized and then become so general and so academically correct
> that there is no point in using them because they
Recently in [1], someone ran into a problem after installing 0.96.
Namely, the 0.95 egg was still on the system, and overriding the 0.96
install.
Could we maybe get a note in the install document to help people out
with this? I forsee lots of people asking about this in the near
future, as more p
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 should have checked Trac first :)
I wo
On 4/28/07, David Larlet <[EMAIL PROTECTED]> wrote:
> I just hope those ones will be successful! Maybe we can learn from the
> past and improve students/dev communication in order to help them a
> bit more if they need it?
I think for the most part, in terms of the scope of GSoC, the previous
one
On 5/29/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> In all seriousness: django.contrib.bikeshed.
>
That actually made me laugh, but I think you have a valid point. This
is definitely a bikeshed topic, but maybe that name can actually work.
django-values provides storage and easy access to v
On 6/26/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I could use a file as cache, yes, but what you're dsecribing wouldn't
> really work well in production environments. To my knowledge, Django
> reloads itself in its entirety if any loaded modules are changed, not
> just a single file. Sure, the
On 8/8/07, John-Scott <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> I'm trying to integrate S3 support into my Django app using
> http://code.djangoproject.com/wiki/AmazonSimpleStorageService for
> now.
>
> I would like to improve the code so that it might be officially
> integrated into Django at
On 8/31/07, jorjun <[EMAIL PROTECTED]> wrote:
>
> Glad though I am that Python has dynamic class attributes, when it
> comes to Django Models, some more discipline could be useful,
> especially when a product is in maintenance phase, IMO.
>
> I recently added the code below to my model definition
On 9/1/07, jorjun <[EMAIL PROTECTED]> wrote:
> But I disagree with __slots__ being justified purely for optimization
> purposes.
Disagree all you want, but this is what Guido Van Rossum, creator of
Python and BDFL, had to say about it:
"__slots__ is a terrible hack with nasty, hard-to-fathom sid
On 1/12/08, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>
> The moderation could be done by member(s) whose time wouldn't be spent
> enhancing django. I used to volunteer on python.org to maintain the
> Python Jobs Board, because I wanted to help out, but I wasn't able to
> contribute in ways that
I originally posted this in -users, but since it deals with internals,
maybe it's more appropriate for -dev.
I'm looking at the FormWizard code, and in __call__, we have the following:
for i in range(current_step):
form = self.get_form(i, request.POST)
if request.POST.get("hash_%d" % i, ''
On Fri, Apr 11, 2008 at 8:03 AM, Honza Král <[EMAIL PROTECTED]> wrote:
> you could perhaps postpone the validation of data till the end of the
> wizard, so only run this once, but that could cause problems for
> example if the user chose to override process_step and do something
> based on the
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
On Sun, Apr 13, 2008 at 6:13 PM, Honza Král <[EMAIL PROTECTED]> wrote:
> > I was going to say "Put the cache into self.foo", but now I'm just
> > realizing that there is just one FormWizard instantiated in urls.py,
> > so different people could be using the same FormWizard instance.
>
> the
76 matches
Mail list logo
