Re: managements.commands and namespace packages
On 11 Feb 2013, at 23:46, Russell Keith-Magee <russ...@keith-magee.com> wrote:
> Hi Alessandro,
>
> On Tue, Feb 12, 2013 at 2:30 AM, Alessandro Dentella <san...@e-den.it> wrote:
> Hi,
>
> this email aims at finding a bettere solution to a problem that was already
> posted some months ago in the user list [1]. If you use namespaces in
> packages to split your code in independently distributable packages as:
>
> jmb.bar
> jmb.foo
>
> you end up not being able to use managements.commands from one of the 2
> packages as the mechanism that finds the packages in
> django.core.management.find_management_module uses imp.find_module that will
> return a tuple containing just one path to one or the other.
>
> IIUC the problem arises since find_module_managements avoids to load all
> modules (efficency concerns I guess) but so doing it misses the .__path__
> attribute on 'jmb' in the example that could be used for the next run of
> find_module.
>
> I personally think that at least as a fallback django should try to import
> the package (or document namespace packages are not supported).
>
> The full answer is somewhere in between; namespace packages aren't supported,
> but that's not (to my knowledge) because we don't *want* to support them --
> it's because nobody has spent the time to make sure they work. Although
> you're obviously hitting a limitation with management commands, I'd be deeply
> surprised if that's the only place that this problem emerges -- Django's
> internal tooling is generally fairly weak (due to lack of testing) when it
> comes to namespace packages.
>
> The following patch works for me, but I'm sure there will be other
> scenarios I'm not considering:
>
> while parts:
> part = parts.pop()
> - f, path, descr = imp.find_module(part, path and [path] or None)
>
> +try:
> +f, path, descr = imp.find_module(part, path and [path] or None)
> +except ImportError:
> +# we're probably dealing with a namespace package
> +if len(app_name.split('.')) >= 2:
> +mod = __import__(app_name + '.management', {}, {}, [''], -1)
> +return mod.__path__[0]
>
>
> I'd be glad to make a patch for this but I wanted to hear if there's any
> better idea.
>
> I'm not sufficiently familiar with namespace packages to be able to comment
> here. However, I'm fairly certain that it will be possible to find canonical
> info on how to handle namespace packages elsewhere in Python's own importing
> tools.
>
> If namespace packages are important to you, then this can be a great way to
> contribute. Open a ticket describing the specific problem (if there isn't one
> already), and turn your snippet above into a proper patch -- the most
> important part of which will be test cases. Management command discovery etc
> are all tested features, but namespace packages aren't currently tested. Even
> if your import modification *isn't* the right solution, tests will still be
> needed.
There is already one such ticket here:
https://code.djangoproject.com/ticket/14087
> Yours,
> Russ Magee %-)
--
David Reynolds
da...@reynoldsfamily.org.uk
--
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: Namspace packages in Django
On 4 Jan 2011, at 20:15, Nils Fredrik Gjerull wrote: > > Hi, Django folks! > > This is my first time posting on the Django developer list. Thanks for > an amazing framework. > > The Distribute build system supports namespaced packages > (http://packages.python.org/distribute/setuptools.html#namespace-packages). > > I have found namespaced packages to be of great help for my use case. A > project I am working on started out with some apps that were specific > for that project. Now I need to create a sub-site that uses only some of > the apps of the original project. I pulled out two of the apps and > created two separate packages for them. Because the apps had quite > common package names I did not want to occupy my namespace with them, so > I put them in a namespace package. This appeared to work correctly until > I tried to put a management command into one of them. The command were > not discovered. I traced this to the find_management_module function in > the django.core.management module. > > I have found a way to discover all management packages without having to > import all the app modules. I tried to do it by importing, but the > manage.py script were running noticeably slower. I have also made a test > case. > > The code is in: > https://github.com/nilsfr/django/blob/pht/django/core/management/__init__.py > https://github.com/nilsfr/django/blob/pht/django/utils/importlib.py > https://github.com/nilsfr/django/tree/pht/tests/regressiontests/admin_scripts > > I do not intend to use this for including different apps with the same > name, in the same project. Only to avoid occupying the namespace with > common names, so I can use the same app name for different projects. > > Any chance of getting this into core? I have a similar problem but with using pkgutil.extend_path(). I have 2 packages set up a bit like this: company/ common/ company/ apps/ news/ management/ commands/ each using the pkgutil.extend_path() trick. However only the first one on the path will be searched for management commands. Hopefully Nils' patch will fix this situation too -- David Reynolds da...@reynoldsfamily.org.uk -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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: ModelForm possible validation bug
Hi, I would really appreciate some feedback on this. Thanks, David On 8 Sep 2010, at 09:39, David Reynolds wrote: > > On 7 Sep 2010, at 16:48, David Reynolds wrote: > >> Hi folks, >> >> I am running into a validation problem with ModelForms - here is a quick >> summary of what is happening > > I have opened a ticket to track this > [http://code.djangoproject.com/ticket/14234]. I'd be happy to work up a > patch, but would appreciate some advice on where it is best to fix it. > > Would it make sense for the ModelForm to unset instanace._adding once a save > has been executed, or is there some other place that would be better suited > for the fix? > > I would also appreciate advice on where to add a test for this issue. > > Thanks, > > David > > -- > David Reynolds > da...@reynoldsfamily.org.uk > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@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. > -- David Reynolds da...@reynoldsfamily.org.uk -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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: ModelForm possible validation bug
On 7 Sep 2010, at 16:48, David Reynolds wrote: > Hi folks, > > I am running into a validation problem with ModelForms - here is a quick > summary of what is happening I have opened a ticket to track this [http://code.djangoproject.com/ticket/14234]. I'd be happy to work up a patch, but would appreciate some advice on where it is best to fix it. Would it make sense for the ModelForm to unset instanace._adding once a save has been executed, or is there some other place that would be better suited for the fix? I would also appreciate advice on where to add a test for this issue. Thanks, David -- David Reynolds da...@reynoldsfamily.org.uk -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
ModelForm possible validation bug
Hi folks,
I am running into a validation problem with ModelForms - here is a quick
summary of what is happening
Take a simple model - here we call Model.full_clean as part of the custom save
method to enforce the validation:
from django.db import models
class Stuff(models.Model):
"""(Stuff description)"""
name = models.CharField(max_length=100)
age = models.IntegerField()
description = models.TextField(blank=True)
def __unicode__(self):
return self.name
def save(self, *args, **kwargs):
self.full_clean()
return super(Stuff, self).save(*args, **kwargs)
Simple ModelForm for the above - nothing unusual here:
from django import forms
class StuffModelForm(forms.ModelForm):
class Meta:
model = Stuff
# Instantiate the form with some data
form = StuffModelForm({
'name': 'Fred',
'age': '56',
'description': 'Old Fred is 57',
})
# Check the form is valid
if form.is_valid():
obj = form.save(commit=False) # save but don't commit
obj.age = 27 # Change the age
obj.save() # Do a full save of the object
obj.name = 'Ted' # Change the name
obj.save() # Attempt to update the db record
# you get this error:
ValidationError: {'id': [u'Stuff with this ID already exists.']}
This happens because the ModelForm sets ModelForm.instance._adding to True and
never cleans it up. This is then tested for in Model._perform_unique_checks
and the uniqueness checks are executed if it is set to True which it always is
after calling ModelForm.save()
Is this a bug? Surely it can't be that unusal to want to call
Model.full_clean() before each save?
--
David Reynolds
da...@reynoldsfamily.org.uk
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@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: Tiny, tiny patch - can it make it into Django 1.2?
On 6 Apr 2010, at 19:54, Jacob Kaplan-Moss wrote: >> Just thought I'd ask whether or not >> http://code.djangoproject.com/ticket/10917 would be able to make it into >> Django 1.2? > > No. It's a feature addition, and we're well past feature freeze. No problem, just thought I'd ask. Sorry for the noise. Thanks, David -- David Reynolds da...@reynoldsfamily.org.uk -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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: EmailBackends
On 22 Feb 2010, at 17:48, Mat Clayton wrote: > We run our own custom EmailBackend, and for the most part the new Email > Backend system has been fantastic, however recently I just found a > limitation, which I'd like to raise briefly to see if anyone else has it, or > can suggest an obvious solution Ive missed. > > We currently have a queued email backend which communicates with external > services to send email on our behalf. When our main newsletters go out, this > causes a huge spike in the system and queues pile up. This is fine except > that we want some email to now bypass the queue, for example registration > emails. This is because the queues often take 3-4 hours to process and this > is an unacceptable delay for signup emails. So essentially we would like to > be able to use a different backend for different circumstances, or be able to > pass args/kwargs into the backend from the send() to allow the EmailBackend > to make the appropriate routing changes. > I guess you need to somehow give your emails a priority, so that you can prioritise your signup emails over the newsletters. You might want to look at how django-mailer [0] does it. 0 - http://github.com/jtauber/django-mailer -- David Reynolds da...@reynoldsfamily.org.uk -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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: Model.objects.raw() (#11863)
Russ, On 29 Sep 2009, at 03:25, Russell Keith-Magee wrote: > (1) know about the trick of instantiating an object with the > unrolled list version of a cursor, and Any chance you could expand upon this? -- David Reynolds da...@reynoldsfamily.org.uk --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Model validation
Hi, I need to use some sort of model validation in a project I am working on and I wondered what that status of http://code.djangoproject.com/ticket/6845 is. Is the github code useable for production? Is there anything I can do to help with it? Is there a recommended workaround for model validation in the meantime? Thanks, David -- David Reynolds da...@reynoldsfamily.org.uk --~--~-~--~~~---~--~~ 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: Ticket #5610 - Useful for dumpdata to be able to use a specific model
On 16 Dec 2008, at 10:53, Russell Keith-Magee wrote: >> From an initial inspection, #5610 looks ready for trunk. The feature > is well defined, and the patch now has docs and tests. I'm knee deep > in aggregation code at the moment, but I'll put this on my todo list. Excellent news, thanks Russ :) > The connection with #4656 is that once you can single out an > individual model to dump, you will want to dump all the dependencies > of that model. Obviously, you could do this by manually specifying all > dependent model names, but providing an easy option to hunt down > dependencies would also be handy. That makes a whole lot of sense I look forward to #4656 hitting trunk too. Cheers, David -- David Reynolds da...@reynoldsfamily.org.uk --~--~-~--~~~---~--~~ 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: twitvn
On 5 Dec 2008, at 19:17, "Eric Holscher" <[EMAIL PROTECTED]> wrote: > Check out http://twitter.com/DjangoTracker > Thanks Eric! I never knew that existed! --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
twitvn
Hi, Since a lot of Djangonauts and Django Developers are using twitter, would anyone find it useful to get svn commit messages on twitter? There seem to be a drop in svn hooks script called twitvn [0] that can be used. I've seen other people following the Wordpress [1] one and thought it might be quite interesting and useful to have one for Django. Thoughts? 0 - http://code.google.com/p/twitvn/ 1 - http://twitter.com/wpdevel -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: logout() method for custom authentication backends
On 1 Dec 2008, at 12:27, Julien Phalip wrote: > I think you could achieve that without patching Django. You could > simply create a custom view which wraps around auth.logout and calls > your other method. That doesn't help if you want to continue using the login/logout views from django.contrib.auth.views -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: logout() method for custom authentication backends
On 1 Dec 2008, at 11:49, David Reynolds wrote: > > I have a custom authentication backend that requires a method to be > run to log out of the system. It would be quite useful if there was a > way > to hook into the django.contrib.auth.logout method to run this custom > method. > > The best way I can think of is to add a logout method to the > authentication backend which is called from within the > django.contrib.auth.logout method. > > Does anyone have any thoughts on this? Would it be useful for any > other backends? I suppose additionally, it might be useful to do the same thing for login too. -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
logout() method for custom authentication backends
I have a custom authentication backend that requires a method to be run to log out of the system. It would be quite useful if there was a way to hook into the django.contrib.auth.logout method to run this custom method. The best way I can think of is to add a logout method to the authentication backend which is called from within the django.contrib.auth.logout method. Does anyone have any thoughts on this? Would it be useful for any other backends? -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Ability to delete contents of FileField and ImageField in admin
On 18 Aug 2008, at 2:56 pm, Brian Rosner wrote: > Keep an eye on http://code.djangoproject.com/ticket/7048. Thanks, Brian. -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Ability to delete contents of FileField and ImageField in admin
Hi, I notice some discussion about this from a while back but as far as I can tell it has all gone quiet. This may be because it has been fixed, or possibly because it has been forgotten about. Can anyone give me a status update of whether or not it is possible to delete the contents of a FileField or ImageField from within the admin? Thanks, David -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Call for testing: streaming uploads (#2070)
.__test__.API_TESTS
Failed example:
[sorted(d.items()) for d in dicts]
Expected:
[[('name', u"Guido's All New House of Pasta"),
('serves_hot_dogs', False)]]
Got:
[[('name', u"Guido's All New House of Pasta"),
('serves_hot_dogs', 0)]]
--
File "/var/www/django/git/django/tests/regressiontests/
model_inheritance_regress/models.py", line ?, in
regressiontests.model_inheritance_regress.models.__test__.API_TESTS
Failed example:
[sorted(d.items()) for d in dicts]
Expected:
[[('name', u"Guido's All New House of Pasta"),
('serves_gnocchi', False), ('serves_hot_dogs', False)]]
Got:
[[('name', u"Guido's All New House of Pasta"),
('serves_gnocchi', 0), ('serves_hot_dogs', 0)]]
--
File "/var/www/django/git/django/tests/regressiontests/
model_inheritance_regress/models.py", line ?, in
regressiontests.model_inheritance_regress.models.__test__.API_TESTS
Failed example:
[sorted(d.items()) for d in dicts]
Expected:
[[('name', u"Guido's All New House of Pasta"),
('serves_gnocchi', False), ('serves_hot_dogs', False)]]
Got:
[[('name', u"Guido's All New House of Pasta"),
('serves_gnocchi', 0), ('serves_hot_dogs', 0)]]
==
FAIL: Doctest: regressiontests.string_lookup.models.__test__.API_TESTS
--
Traceback (most recent call last):
File "/var/www/django/git/django/django/test/_doctest.py", line
2180, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for
regressiontests.string_lookup.models.__test__.API_TESTS
File "/var/www/django/git/django/tests/regressiontests/
string_lookup/models.py", line unknown line number, in API_TESTS
--
File "/var/www/django/git/django/tests/regressiontests/string_lookup/
models.py", line ?, in
regressiontests.string_lookup.models.__test__.API_TESTS
Failed example:
Foo.objects.get(friend__contains=u'\xe7')
Exception raised:
Traceback (most recent call last):
File "/var/www/django/git/django/django/test/_doctest.py",
line 1267, in __run
compileflags, 1) in test.globs
File "", line
1, in
Foo.objects.get(friend__contains=u'\xe7')
File "/var/www/django/git/django/django/db/models/manager.py",
line 82, in get
return self.get_query_set().get(*args, **kwargs)
File "/var/www/django/git/django/django/db/models/query.py",
line 287, in get
% self.model._meta.object_name)
DoesNotExist: Foo matching query does not exist.
--
File "/var/www/django/git/django/tests/regressiontests/string_lookup/
models.py", line ?, in
regressiontests.string_lookup.models.__test__.API_TESTS
Failed example:
Foo.objects.get(friend__contains='\xc3\xa7')
Exception raised:
Traceback (most recent call last):
File "/var/www/django/git/django/django/test/_doctest.py",
line 1267, in __run
compileflags, 1) in test.globs
File "", line
1, in
Foo.objects.get(friend__contains='\xc3\xa7')
File "/var/www/django/git/django/django/db/models/manager.py",
line 82, in get
return self.get_query_set().get(*args, **kwargs)
File "/var/www/django/git/django/django/db/models/query.py",
line 287, in get
% self.model._meta.object_name)
DoesNotExist: Foo matching query does not exist.
--
Ran 264 tests in 852.132s
FAILED (failures=5)
--
David Reynolds
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
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 PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
Re: Experimental Git repository available
On 19 Jun 2008, at 6:07 pm, Jacob Kaplan-Moss wrote: > If you know the correct incantation to add other git-svn-created > branches, feel free to school me :) I think Brian Rosner covered pulling in all branches from svn on his screencast about django and git [0] but I can't off the top of my head remember how he did it. http://oebfare.com/blog/2008/jan/23/using-git-django-screencast/ -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Email from Trac
Hi, Are emails from trac still working? As I've had a ticket closed and another commented upon and not received email from these. Is something not working? Thanks, David -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: #django registration
On 28 Dec 2007, at 7:06 am, Collin Grady wrote: > > I've never bothered bringing this up before as it's never really been > needed, but tonight we had someone with a rogue script in their IRC > client which prevented them from closing their client, and flooded the > channel with "hello world" for a minute and a half solid :) > > It would've been very helpful to have ops in the channel to boot him > after it started until he fixed it, but as the channel is currently > unregistered, we had to just wait it out :) > > I understand that people are likely still on vacation right now, > and it > isn't urgent that it be done soon, I just wanted to bring it to > mind so > maybe it could be dealt with in the new year if someone has some spare > time :) I did bring up a similar thing on django-users in November: http://groups.google.com/group/django-users/browse_thread/thread/ 7fd54d4fa0c1d97f/799ef2412b81ff79 But nothing was ever done.. -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Why the request.get_full_path() returns empty string
On 10 Dec 2007, at 5:35 am, Eratothene wrote: > Don't bother I have just figured out why. Can you say why, just for completeness of the archives? Thanks, David -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Django 1.0 features -- the definitive list
On 30 Nov 2007, at 6:33 am, Adrian Holovaty wrote: > My second reason for choosing 2.0 is, shall we say, less wholesome. > After having endured a 2.5+ year deluge of "When is 1.0 coming out?" > blog entries, comments, e-mails and in-person confrontations from > people all around the world, I would find it incredibly satisfying, in > a devilish way, to release this thing and slap a "2.0" on it. It would > underscore the project's stability while at the same time > demonstrating that version numbers are completely arbitrary. Worth it just for this reason alone IMO ;) -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Comments system for sprint?
On 15 Nov 2007, at 4:24 pm, Ryan K wrote: > > I've just implemented the django.contrib.comments system for my site > which is actually a great package that doesn't seem to be used by many > people. Does anyone have any plans to update the system? Some basic > configuration stuff seems to be missing like the ability to configure > where the comment's templates are located and what they are named. It > also uses the oldforms library. I've never worked on any part of the > Django codebase and I'm not sure if it already has plans for overhaul > but I would like to make the package more configurable for the sprint. > Any thoughts? Ryan, Search trac[0] to see if there are any open tickets about the things on the comments app that you want to fix. If there are, claim the ticket and set to work on fixing them. If there isn't any tickets relating to it, add one, claim it and set to work :) 0 - http://code.djangoproject.com/query -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: ANN: Django sprint, December 1st
Jacob Kaplan-Moss wrote: > Howdy folks -- > > We had such a great time doing that last sprint, so we're doing it again! > > We'll hold the sprint Saturday, December 1st here in Lawrence, KS, and > virtually around the world. We'll run things much the same as we did > last time: Hurrah! Sprinting in the holiday season! ;) -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
guidance on #5737
Hi, I've just added this ticket (#5737), which I am quite keen to fix, as it would be useful for the project I'm currently working on, can anyone give me any advice as to whether this is something that can be fixed and where I should look to fix it? Thanks, David http://code.djangoproject.com/ticket/5737 -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Discussion on #5610 - addition to dumpdata to specify model
On 27 Sep 2007, at 1:07 am, Russell Keith-Magee wrote: > Sounds like a good idea to me. It would dovetail nicely with the > proposal from ticket #4656. > > Want to try your hand at a patch? Sure, do you think the way I suggested it working would be right? ie: ./manage.py dumpdata product.Category or is there a better way, in case you want to do more than one model from an app? Thanks, Dave -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Discussion on #5610 - addition to dumpdata to specify model
On 26 Sep 2007, at 4:07 pm, David Reynolds wrote: > > Hi, > > Would anyone else find this useful? > > I'm quite happy to take a shot at it, if anyone else will find it of > any use. Just to clarify: http://code.djangoproject.com/ticket/5610 Anyone any thoughts? Thanks, David -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Discussion on #5610
Hi, Would anyone else find this useful? I'm quite happy to take a shot at it, if anyone else will find it of any use. Thanks, David -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: mod_python documentation issues
Graham,
It was me that closed it, at the advice of Malcolmt and Russellm. If
you'd like to send me your patch, I'd be happy to attach it to the
ticket. I'd quite like to see the context of where you'd put your
suggestions as it kinda seems like it's already covered in what's there.
Thanks,
David
Graham Dumpleton wrote:
> On Aug 30, 9:34 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>> On 8/29/07, GrahamDumpleton<[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>> Seems I can no longer add to Django tickets as the system rejects me
>>> saying I am trying to submit spam, so posting here instead.
>> I posted for you, including you on ticket
>> CC:http://code.djangoproject.com/ticket/5299
>
> Seems I am never going to win on this issue. Latest updates have seen
> the issue closed without any change being made. I also again can not
> put updates on the ticket since I seem to be completely blacklisted or
> something from Django site as I always get 'Submission rejected as
> potential spam (Akismet says content is spam)' no matter what I do. I
> give up. Someone else can answer user questions where this is the
> issue now. :-(
>
> Below is the response I tried to submit when it was rejected:
>
> Your average user is not going to know that that extends to module
> paths mentioned in urls.py. ie., it isn't obvious that if instead of
> using:
>
> {{{
> (r'^articles/(\d{4})/$', 'weblog.news.views.year_archive'),
> }}}
>
> you use:
>
> {{{
> (r'^articles/(\d{4})/$', 'news.views.year_archive'),
> }}}
>
> that you must therefore have:
>
> {{{
> PythonPath "['/usr/local/django-apps','/usr/local/django-apps/
> weblog', , '/var/www'] + sys.path"
> }}}
>
> ie., that both parent of site directory and the site directory need to
> be added to PythonPath.
>
> Even then, it also isn't obvious when doing an import in a module in a
> subdirectory either. This is because both things just work when the
> development server is used as was explained in the list post. That
> questions keep coming up occasionally where this is the issue, means
> the documentation isn't clear enough.
>
> It would make it a lot better if the above example of both site parent
> directory and site directory were included with the statement that
> both directories would need to be listed where the name of the site is
> not mentioned within rules in urls.py, or where a module in a
> subdirectory imported a module with referencing through the site root.
>
>
>
> >
--
David Reynolds
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
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 PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
Re: Let's schedule a Django sprint
On 5 Sep 2007, at 9:32 pm, Adrian Holovaty wrote: > I propose Friday, September 14. Some reasoning: I'm not wholly familiar with how sprints work, but if there's a need for testers, I can be around a bit on Friday and at the weekend. Thanks, David -- David Reynolds [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
