Re: Backport for ticket 34063?

t and its importance in moving Django forward mitigates for an exception to the backport policy. Cheers, Kevin On Friday, December 30, 2022 at 5:24:51 PM UTC-5 timog...@gmail.com wrote: > As perfectionists, it's always hard to say (and hear) "no" when this sort > of request comes up.

Re: Stop QuerySet repr from executing queries

aluated]>" QuerySet.__repr__ = __repr__ ``` If folks are willing to reconsider their positions on this issue, I am more than willing to do what is necessary to contribute this change upstream, so that others are not impacted by this in the future. Thank you, Kevin On Tuesday, March

Re: Difference between AdminSite.admin_view and staff_member_required?

`staff_member_required` is a nice convenience method, quite useful outside of the admin if your authorization needs are sufficiently served by User.is_staff (which isn't always the case of course, but often *is* on a small project). Yes, it can be reduced to a `user_passes_test` call, but

Re: Proposal: Drop dependency on pytz in favor of zoneinfo

work for Django. Cheers, Kevin On Friday, October 9, 2020 at 8:06:49 AM UTC-7 Paul Ganssle wrote: > Before looking at alternatives, I wonder if we can just change the shims > package to make it fully backwards compatible? Right now the shims version > of normalize() > <https://g

Re: Proposal: Drop dependency on pytz in favor of zoneinfo

adjust the time the way pytz does? Perhaps by wrapping pytz itself, and calling its normalize() from the corresponding pytz timezone; or by simply replicating its time-changing logic? Apologies if that's a naive question. Cheers, Kevin On Thursday, October 8, 2020 at 11:35:21 PM UTC-7 smi...

Re: Proposal: Drop dependency on pytz in favor of zoneinfo

one perspective, of course...) Cheers, Kevin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+

Re: Proposal: Drop dependency on pytz in favor of zoneinfo

hat should happen (e.g. a feature flag), or when it should happen. Cheers, Kevin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails f

Dynamic SESSION_COOKIE_DOMAIN and CSRF_COOKIE_DOMAIN settings

feelings one way or another before moving forward with a PR. Cheers, Kevin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, sen

Re: Django reusable app versions.

You are totally right, my mistake. Sorry about that, noob here. On Tuesday, November 12, 2019 at 12:16:12 PM UTC-6, Adam Johnson wrote: > > Hi Kevin, > > I feel like this is a support question more than a question around > developing Django, so I've pasted my canned response below

Django reusable app versions.

Hi, I'm new to Django so excuse me if it's a noob question. I have a Django app, let's call it "project", that uses a Django reusable app, let's call it "app", version controlled on github, and tagged. 1. I create a first version of the app with its initial 0001_initial.py migration file, tag

Re: Pre-proposal: adopt dj-database-url as a DEP 7 official project

ently able to volunteer to do it, so I'm working on the assumption that dj-database-url retains more or less its present scope. Kevin On Thursday, July 18, 2019 at 12:46:13 PM UTC-4, Jacob Kaplan-Moss wrote: > > Hi folks - > > I’d like to gauge interest in adopting dj-database-url

Oracle sequence naming regression - input on approach?

a template? Thanks, Kevin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegro

Re: Improving Windows users experience at the command line

agree that it would nice to have a Windows-native solution that Just Works, so +1 from this occasional Windows user. Cheers, Kevin [1] https://bugs.python.org/issue22343 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to D

Re: Should we require pytz for timezone support in Django?

I agree with requiring pytz if you have timezone support enabled in Django, as that cuts out a set of edge cases and likely simplifies the code base a bit in the long run. And I even agree with forcing it to be installed with Django if we want to encourage people to use Django with timezone

Re: change commit message format to present tense?

d make a difference in your native language? For what it's worth, I'm in favor of both proposed changes. Cheers, Kevin On Saturday, June 25, 2016 at 9:29:15 PM UTC-4, Tim Graham wrote: > > Reinout, I agree that the imperative mood seems awkward, especially when > reading history, but o

GitHub Issues for DEP repository?

Hello, With all the talk of DEPs flying around I thought I'd finally take a look at one in detail. I wanted to make a suggestion about it and realized that there wasn't really a good place to do so. The issue was too minor for a mailing list discussion, and there was no open pull request to

Re: ***SPAM*** Re: Middleware+Transactions:

Thomas, did you ever find a solution to your problem? I'm having similar thoughts and am looking for an answer. On Friday, February 6, 2015 at 4:18:53 AM UTC-8, guettli wrote: > > > > Am 04.02.2015 um 14:04 schrieb Anssi Kääriäinen: > > I'd really like to be able to define middlewares that

Re: Value of tightening URLValidator/EmailValidator regular expressions?

Validation that doesn't rely on browser behavior *is* useful, if only for the (admittedly shrinking, but still non-zero) population of folks using older browsers. Also API clients and so forth. Very much agreed that it should match the HTML5 spec, though - fewer edge cases and more predictable

Re: Migrations in Django 1.7 make unit testing models harder

I have found a good alternative to the old initial data feature. It's called django-update-initial-data. https://github.com/ambitioninc/django-dynamic-initial-data MySQL compatible version: https://github.com/minervaproject/django-dynamic-initial-data/tree/mysql It's actually better than the

Re: Request for help: building a docker/vagrant platform for running Django's test suite

Later than expected, but here we go folks: https://github.com/archen/django-tests There are some barebones instructions for contributing and direction. Feel free to reach out to me directly for any assistance or questions so I can better document the process for anyone else interested in

Re: Request for help: building a docker/vagrant platform for running Django's test suite

e a crack at this and think its best > to not duplicate efforts. Let me know how I can pitch in. > On Wednesday, April 22, 2015 at 10:25:17 PM UTC+5:30, Kevin Glavin wrote: >> >> Thank you everyone for your interest. I spoke with Tim last night to start >> piecing together the

Re: Request for help: building a docker/vagrant platform for running Django's test suite

Thank you everyone for your interest. I spoke with Tim last night to start piecing together the strategy. The gameplan on my end is to start a repo that we can all work from and (in)formally define the high level strategy. I'll enter any work items as issues on the github repo and share the

Request for help: building a docker/vagrant platform for running Django's test suite

Hi Tim, I have been using Docker, Vagrant, and Jenkins for a while now independently. Would love to help out with this effort. Feel free to reach out to me privately if you'd like to continue the discussion. -- You received this message because you are subscribed to the Google Groups "Django

Re: Unneeded index created with unique=True and db_index=False in TextField

This issue was the subject of https://code.djangoproject.com/ticket/24082. There, the accepted (but not implemented) solution is the same as suggested here: allowing the user to opt out of the creation of the additional index with `db_index=False`. On Wednesday, April 15, 2015 at 2:11:25 PM

[GSoC] Security Dashboard

developer. Links: Fun Project - https://github.com/kburts/drf-music Website / blog - http://kevinburton.ca/ Github - https://github.com/kburts Thanks for reading & your feedback, Kevin -- You received this message because you are subscribed to the Google Groups "Django develop

Re: Two proposals for the Django Code of Conduct.

On Wednesday, September 10, 2014 10:39:51 AM UTC-4, Josh Smeaton wrote: > > Kevin, > > > It simply says, in deliberately vague language, that if a member of the > Django community is treated abusively by another member of the Django > community _outside_ a Django

Re: Two proposals for the Django Code of Conduct.

o you have an opportunity to surprise me there. Regardless, your criticism has provided me with the opportunity to more thoroughly think through and explain my rationale behind this change. For that I thank you. Kevin On Tuesday, September 9, 2014 3:29:25 PM UTC-4, Benjamin Scherrey wrote: &

Re: Two proposals for the Django Code of Conduct.

eate the ASBO, could > it be called the Anti-Social Django Act? > > On Tue, Sep 9, 2014 at 7:33 AM, Benjamin Scherrey <prote...@gmail.com > > wrote: > >> Hi Kevin, >> >>And thanx for responding to my question about the need for such a >> poli

Re: Two proposals for the Django Code of Conduct.

y made the right choice. On Monday, September 8, 2014 9:37:16 PM UTC-4, Russell Keith-Magee wrote: > > Hi Kevin, > > Thanks for these suggestions. > > By way of settings expectations - a patch of this nature has a little more > procedural overhead than a normal patch, because it

Django Project Proposal

My name is Kevin Sebastian and I have been working with django for quite some time and I would like to contribute to any of its projects.I will be grateful if someone can offer any suggestion for the same.I am also proficient in python and its various libraries and I have worked on python

Re: [GSoC] Switching to Jinja2 proposal

> > What kind of support do you except for third-party template tags? Suppose, > that > `cycle` tag is not builtin. Would it be acceptable to write sth like that: > > dtl cycle '1' '2' as rows > > It could be quite easily implemented as a Jinja2 extensions. Of course, I > guess > that you'd

Re: [GSoC] Switching to Jinja2 proposal

. :-) And if you're forced to prioritize, I think that would be more useful than being able to inherit from DTL templates. Cheers, Kevin > > - It would be nice to use the same loaders for both django.dtl and > jinja2. This >requires to rewrite existing Django loaders so th

Re: [GSoC] Switching to Jinja2 proposal

Russell makes the very good point that Jinja2 isn't just a faster version of the Django template engine - it's philosophically at odds with the original design and intent of the Django template engine. Personally, I prefer Jinja2's approach and would love to see it become the standard. (The

Re: Renaming apps.has_app

+1 for "is_installed" I don't find the grammar objectionable here, just think of it as "is_(each one of these apps)_installed" On Sunday, January 5, 2014 3:50:45 PM UTC-6, Aymeric Augustin wrote: > > On 5 janv. 2014, at 22:38, Raffaele Salmaso > > wrote: > > > Should

TestCase can produce surprising failures

ers who may not know anything about transaction management (and who are probably also the least likely to need the faster tests). Are we leading them into a premature optimization? Cheers, Kevin [1] https://code.djangoproject.com/ticket/21540 -- You received this message because you are subscribed

Re: Revert 165f44aa?

s. I think this is Marc and Florian's suggestion. The problem here is that the grouping of with statements depends on both logical and lexical considerations, which seems somewhat less readable to me. 4) Revert the commit and stick with one with statement per line. Personally, I prefer 4 or

Re: [GSoC] Revamping validation framework and merging django-secure once again

> > > We probably cannot move checks of `primary_key` and `unique` living in > `FileField.__init__`. We test if one of these two parameters was passed; we > don't check their values. Consider that an user passes unique=False. This > is > the default value, but nevertheless, this should result in

Re: Order of INSTALLED_APPS

don't think it would break South installations as custom app commands > will always override builtins. Could you open a ticket for that? The > inconsistency is problematic. Obviously it would be backwards incompatible, > but we need to gauge the size of the impact. > > Marc > On

Re: Order of INSTALLED_APPS

mands were consistent with the other cases, but that would create serious backwards compatibility issues. Like, breaking everyone's South installation. :-O Cheers, Kevin On Wednesday, August 14, 2013 5:26:47 AM UTC-4, Stefano Crosta wrote: > > Done! https://code.djangoproject.com/ticket/20914#t

docs.djangoproject.com very slow

Not sure where to report this, but the docs.djangoproject.com is going very slow today, and I received a "504 Gateway Time-out" from the nginx server. Any ideas? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this

Re: Epydoc failed to generate documentation for Django 1.5

like CRUD and how to make it extendable. it uses docstrings, which provide additional info on the classes and methods themselves. On Wednesday, 3 April 2013 22:26:06 UTC-5, Jacob Kaplan-Moss wrote: > > On Wed, Apr 3, 2013 at 10:19 PM, Kevin Veroneau > <kver...@gmail.c

Epydoc failed to generate documentation for Django 1.5

the entire Django project using Epydoc to see how that would look. Seeing these UML graphs is memorizing and very educational for when working with Django. Is this Epydoc error related to Epydoc or something that Django shouldn't have done in it's source code? Best Regards, Kevin Veroneau

Why doesn't DjangoProject.com downloads provide a Windows installer like web2py does?

. Link to retained InstantDjango(for example purposes): http://www.pythondiary.com/blog/Apr.10,2012/instant-django-release-information.html I plan on updating this InstantDjango with Django 1.5, and using distribute over setuptools. Current Download count: 1461 Best Regards, Kevin Veroneau

Re: Class-based view improvement idea

Scratch this, I just noticed that the dev docs explain a lot more than the 1.3/1.4 docs do. Perhaps having this documentation in 1.3/1.4 as well, or at least mentioning there that the dev docs contain much more information. On Sunday, 11 November 2012 11:31:41 UTC-6, Kevin Veroneau wrote

Class-based view improvement idea

an example of what I would love to see in a future version of class-based views. Best Regards, Kevin Veroneau Python Diary http://www.pythondiary.com/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion

Re: Subversion + Django

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

Re: Template Engine Compilation and Runtime Refactoring Progress

Has the repository been deleted? https://github.com/mitsuhiko/django-template-compilation is giving me a 404. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Confused by __unicode_cast and __str_cast in django.utils.functional

__unicode_cast function need to call *unicode* on *self.__func(...)* like what __str_cast does,call *str* function? Any help is appreciated. Kevin Xiao -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email

Re: Could the comments framework be more generic?

at the best way to do this would be, but I should have plenty of time this week to look into it. Cheers, Kevin -- 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.

Re: Could the comments framework be more generic?

Whoops, url should be https://bitbucket.org/bolhoed/django_disqus_comments. On Nov 28, 7:29 pm, Kevin Renskers <i...@bolhoed.net> wrote: > The existing apps use the JavaScript interface offered by Disqus. This > does not integrate with apps that expect Django's comments app. > &

Re: Could the comments framework be more generic?

://bitbucket.org/bolhoed/django-disqus-comments/. I think that from this code the problem of the current situation is clear. I'd be more then happy to work on a new comments API for Django by the way! Kevin On Nov 28, 5:19 pm, "subs...@gmail.com" <subs...@gmail.com> wrote: &g

Could the comments framework be more generic?

. Django-blog-zinnia does this. I am looking forward to any comments and ideas. Is something like this even possible without completely breaking backwards compatibility? Kind regard, Kevin Renskers -- You received this message because you are subscribed to the Google Groups "Django developers&q

Re: #12012 Logging: Final call for comments

> >> These are fairly minor modifications, so I'm still intending to commit >> early next week, barring major objections. >> > > As per my answer to Kevin - I think a NullHandler addition to the > 'django' logger needs to happen internally (not under a site > develo

Re: #12012 Logging: Final call for comments

= logging.getLogger('adsf') if not logger.handlers: dictConfig(settings.LOGGING) I feel like that check is unnecessary anyhow... but I guess that's how you'd do it if it is necessary. -k On Fri, Oct 1, 2010 at 8:54 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > On Oct 1, 3:45 am, Kevin

Re: Error email flooding on high traffic production sites

I feel like something like this would be better suited to be in an external application... since it will fail without a cache-backend. Also, the implementation will have to change as Russell is about to commit a logging patch with ticket #12012. This would be best suited though for a custom

Re: #12012 Logging: Final call for comments

re: verbose logging configuration. This bothered me as well initially, though after starting to use logging extensively I realized that there isn't really a more concise way to provide all of the features that the logging config brings to the table. We can however, create a very concise default

Re: Error email flooding on high traffic production sites

for debugging. Though this is more of a poor excuse for me to work with websockets and rabbitmq, I think it could be useful. Thoughts? Anyhow... here's the current project... If anyone has feature requests... feedback.. criticism ... i'm always game. http://github.com/kevin/django-lumberjack On Thu

Re: 1.3: Start deprecating mod_python?

Could be good to include some text about using the python loggers on that WSGI debug page, rather than relying on the apache logging mechanisms. In django land ... there's django-devserver, django-debugtoolbar, and django-lumberjack. All of them more or less share the same profilers and such.

Re: MySQL index hints

> For a very high traffic project backed by 20+ DB servers Slightly OT, but MySQL performance related... If you are write heavy, there's another issue that I imagine would bring significant gains on a MyISAM setup of that proportion... and possibly other databases to a lesser degree (the locking

Re: Imports in the tutorial

"I agree, and while we're at it also change the settings.py template to just point to urls instead of project_name.urls" Indeed, always the first thing I change when I start a project... Having the project_name there means you are including the directory above your project in the python path in

Re: Beating on an old issue; counter intuitive cascade deletes on foreign keys

This abstract base class likely is a bit less performant than having in-db support for cascades in pgsql... though it should give you the behavior you are seeking. It should set to default, or null if allowed. Enjoy. -k class ClearOnDelete(models.Model): def delete(self):

Re: exception handling memory leak...

This was not a "hey you guys are lazy", actually came across it ... after I had fixed the same issue. I just posted a patch for you generated off trunk... and left a hopefully somewhat entertaining explanation of the details surrounding the issues. -k -- You received this message because you

exception handling memory leak...

http://code.djangoproject.com/ticket/10758 Can we fix this? It's a pretty easy fix. thanks, -k -- 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

Re: Logging in Django

I added a AdminEmailHandler to my branch and pulled the upstream changes. http://github.com/kevin/django-experimental/ It now behaves very close to how django-trunk does on exception ... by default there is a streamhandler pushing to stderr and the admin email handler pushing emails to admins

Re: Logging in Django

if that's what you assumed ... it should be caught by the default apache loggers at minimum, or be sent to your vhost log if you have logging setup per virtual host. -k On May 28, 8:30 pm, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > On May 28, 10:27 pm, Kevin howerton <kevin.hower...@gmai

Re: Logging in Django

ault spits everything out to stderr which is in turn picked up by apache's logging. btw... My implementation of logging is here: http://github.com/kevin/django-experimental and a flushed out demo of what a third party app that utilizes python logging is here (basically just django-devserver with

Re: Logging in Django

I see the utility of being able to have additional ways to setup the logging, though as it is I think the biggest issue people have with the logging stuff is that the dictconfig is already fairly intimidating looking. If someone really wants to disable the default setup of logging, it should be

Re: logging?

M, Karen Tracey <kmtra...@gmail.com> wrote: > On Wed, May 5, 2010 at 12:46 PM, Kevin Howerton <kevin.hower...@gmail.com> > wrote: >> >> What I was suggesting in my post though, was that we alter the default >> CRITICAL error handling behavior ... as it sta

Re: logging?

I did. On Wed, May 5, 2010 at 12:56 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > On Wed, May 5, 2010 at 11:48 AM, Kevin Howerton > <kevin.hower...@gmail.com> wrote: >> ps.  I don't want to get into a flamewar > > Then next time leave out the rambl

Re: logging?

because it was written in ruby, or targets rails, or runs on the JVM, or uses CamelCase for function names is stupid. On Wed, May 5, 2010 at 4:17 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > > On May 5, 4:47 am, Kevin Howerton <kevin.hower...@gmail.com> wrote: > > I th

Re: logging?

because it was written in ruby, or targets rails, or runs on the JVM, or uses CamelCase for function names is stupid. On Wed, May 5, 2010 at 4:17 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > > On May 5, 4:47 am, Kevin Howerton <kevin.hower...@gmail.com> wrote: > > I th

Re: logging?

because it was written in ruby, or targets rails, or runs on the JVM, or uses CamelCase for function names is stupid. On Wed, May 5, 2010 at 4:17 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > > On May 5, 4:47 am, Kevin Howerton <kevin.hower...@gmail.com> wrote: > > I th

logging?

Realized today that by default django more or less suppresses errors sent to stderr when debug is off. Well I guess it uses email sent to admins by default. Though, I distinctly remember stderr being sent into my apache logs for some reason. Maybe this was when I was using mod_python rather

Re: managing javascript and css resources

>Nothing I've seen so far solves, or even addresses the original need for >_not_ sourcing the same script numerous times (thanks to widgets with >their own media) The widget and admin media system needs to be re-evaluated IMO none of these solutions are going to address the flaws you are

Re: managing javascript and css resources

The django-compress looks a bit better as it has the option to do the versioning (based on a file hash), compression, and concatenization with a management command. Django_compressor does this all on page load, which is not production worthy IMO. Generating an MD5 hash on page load is un-needed

Re: Cujo .... an experimental branch of django.

>From the github: "* Commits should be atomic: they should each encompass a single logical change that works on its own. You can use "git rebase --interactive" to collapse multiple commits into a single commit before pushing your code up for contribution." I think the idea is to

Re: managing javascript and css resources

"I understand that Django has historically been anti-javascript-framework-blessing, and I'm wondering if opening this can of worms would mean having to incorporate some kind of a pluggable backend system (for working with different frameworks, or multiple frameworks at a time) - something I've

Re: Cujo .... an experimental branch of django.

Thanks for the support Russ... I think Cujo (the name at least) has been abandoned and I have joined my efforts with some other developers also interested in contributing to an experimental branch. http://github.com/tomxtobin/django-experimental

Cujo .... an experimental branch of django.

Cujo... for starters it's Amon Tobin's first moniker (he remixes jazz into some delightful tunes, if you don't know of him I strongly recommend you go to your local record store and pick up a copy of "Adventures in Foam"). Also, I felt it was somewhat apt due to the rabid nature of the

Re: High Level Discussion about the Future of Django

"That is, in fact, our policy. 1.1 is compatible with 1.0; 1.2 with 1.1; etc." 1.1 and 1.2 are by definition not point releases. Point releases don't introduce new features. On Thu, Apr 15, 2010 at 3:32 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > On Thu, Apr 15, 201

Re: Pass Thru Image Proxy Patch Interest?

Why not just use the backend feature that already exists? I have an S3 backend that does this... It checks if it's on S3, if not it serves it locally. If it's on S3 it throws the url into memcache, and bob is your uncle. On Wed, Apr 14, 2010 at 9:27 AM, Russell Keith-Magee

Re: High Level Discussion about the Future of Django

"You seem to be suggesting that a fork will somehow magically fix the speed of Django development. I ask you: who is going to work on this fork?" I think a hostile fork is almost a certain outcome if development continues as it has. Not only is the resistance to make backwards incompatible

Re: Inappropriate behavior [was: Re: default delete() clear() behavior and you.]

henceforth, as it clearly doesn't translate well on the internet. sorry again. -k On Tue, Apr 6, 2010 at 12:14 AM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > On Mon, Apr 5, 2010 at 1:06 PM, Kevin howerton <kevin.hower...@gmail.com> > wrote: >> ps.  I didn't really

Re: default delete() clear() behavior and you.

ject.com/ticket/7539 > > But I like your imagination, or is there more truth behind your story > than you'd admit? > > Cheers, > Florian Apolloner > > On Apr 5, 8:06 pm, Kevin howerton <kevin.hower...@gmail.com> wrote: >> Hi. >> >> So I came across a

default delete() clear() behavior and you.

Hi. So I came across a use-case for wanting to delete content (which django doesn't really handle exactly to my liking). I just got back from a vacation in vegas and noticed in a drunken stupor I had posted some pictures on my blog that should I really shouldn't have (

Re: Deprecating psycopg 1

On Dec 12, 5:09 pm, Jacob Kaplan-Moss wrote: > > I prefer to think of it like this: > > Django 1.2 ships. Users read the release notes, and notice that > psycopg1 is now deprecated and will be removed. It's still there, and > still supported, so they can upgrade quickly and

Re: project folder with dots

On Oct 26, 7:23 pm, Tobias McNulty wrote: > > IMHO the project namespace is a useful one to keep around. If you lose the > project name space, then you risk polluting your python path with a lot of > generic 'urls' modules, among other things. > > If your directory

Re: Off Topic: Where to discuss web application frameworks in general

On Oct 21, 3:43 am, maxky wrote: > > I know, that this is not the right place for that discussion. Can > anyone redirect me > to the adequate bb or usenet group? Python's Web-SIG list is the best place for asking questions that will be read by a variety of different Python

Re: Brand new projects should pass their tests (the django.contrib.auth thing from #7611)

On Oct 6, 1:43 am, Simon Willison wrote: > > Option 6 would be welcome if anyone has any ideas. > Do what Grok does: $ grokproject newapp $ cd newapp $ ./bin/test Running tests at level 1 Total: 0 tests, 0 failures, 0 errors in 0.000 seconds. That is, if it's a

Re: Replacing get_absolute_url, I am against it

> If the objective is to seperate the two systems why is having the URL > system know about Models more acceptable than having the Model system > know about URLs?  This is most certainly a bike shed IMO. > > Alex Because it's the URL system which is making those models available on the web, not

Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

> > Thanks, the accompanying discussion is very interesting and on point. > > But as someone there points out, why stop at widgets? > > Because customizing widgets is a common request, unlike other attributes. But customizing fields is quite common, no? I agree that it's rare that you will want

Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

> Please file a ticket for the documentation fix it would be greatly   > appreciated. :-) Will do. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

better solution. Cheers, Kevin --~--~-~--~~~---~--~~ 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

Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

. But unless there's a groundswell of support for my position, I guess I'll just file a documentation ticket. Cheers, Kevin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To po

Shouldn't custom fields in ModelForms pick up model Field options by default?

Take a simple Model and ModelForm like this: class Author(models.Model): name = models.CharField(max_length=80, blank=True, default="Joe", help_text="A name") class AuthorForm(forms.ModelForm): class Meta: model = Author The resulting form will reflect the desired help text,

[GSOC-Testing] Double Update!

access to e-mail, and will be checking when possible. Hopefully the end of next week will be the end of most documentation/testing efforts, and I can give people the go-ahead to start trying to mess around with everything! -- Kevin Kubasik http://kubasik.net/blog

Re: Tests for TestCase

ng for existing tests of > django.test.TestCase (not tests that use django.test.TestCase, but a > test that verifies the TestCase class itself is working properly), and > haven't been able to locate them. Any pointers on where I can find > these? Or do they not exist? > > Much th

[GSOC-Testing] Twill Runner and Updates!

on bugs/behavior inconsistencies that have been popping up. Otherwise, not much to report, this weekend will probably be pretty code-tastic (if I get a chance). I'll post a link to the list once I get the test/sample project done and share the code! Cheers! -- Kevin Kubasik http://kubasik.net

[GSOC-Testing] Kubasik Status Update

at djangocon. Would there be interest? -- Kevin Kubasik http://kubasik.net/blog --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-

[GSOC-Testing] Update

was the creation of a twill testrunner. I will probably get to that sometime next week, along with more complete testing of the new features rolled in this week. The update comes in a day early, since my 4th weekend starts a day early and I won't be coding much tomorrow! Happy 4th! -- Kevin

  1   2   >