Re: Does Python 2.6.5 broke Django 1.1.1 Client Test?
Marcob wrote: > Please, does anybody know which patch I need to apply to 1.1.1 to fix > this strange problem? http://code.djangoproject.com/changeset/12807 ? -- ()_() | That said, I didn't actually _test_ my patch. | + (o.o) | That's what users are for! | +---+ 'm m' | (Linus Torvalds) | O | (___) | raffaele dot salmaso at gmail dot com | -- 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: Templates by app
On 20 March 2010 12:48, wrote: > You can use both schemes. Defaults in app/templates, overrides of defaults in project/templates. HM -- 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: Templates by app
> > You can use both schemes. > > Defaults in app/templates, overrides of defaults in project/templates. You want to use both places to store templates? Look at TEMPLATE_LOADERS: TEMPLATE_LOADERS = ( 'django.template.loaders.filesystem.load_template_source', 'django.template.loaders.app_directories.load_template_source', ) TEMPLATE_DIRS = ( SITE_BASE + '/templates' ) -- 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: Does Python 2.6.5 broke Django 1.1.1 Client Test?
On Mon, Mar 22, 2010 at 4:07 AM, Raffaele Salmaso < raffaele.salm...@gmail.com> wrote: > Marcob wrote: > > Please, does anybody know which patch I need to apply to 1.1.1 to fix > > this strange problem? > http://code.djangoproject.com/changeset/12807 ? > > No, turns out it was a change made farther back, and it was in fact a change specifically in response to the change in Python: http://code.djangoproject.com/changeset/11821 Karen -- 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: Does Python 2.6.5 broke Django 1.1.1 Client Test?
On Mar 22, 1:53 pm, Karen Tracey wrote: > No, turns out it was a change made farther back, and it was in fact a change > specifically in response to the change in Python: > http://code.djangoproject.com/changeset/11821 Karen, thanks! :-) Btw, I think this is a users-developers-gray-area-thread :-) Ciao. Marco. -- 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.
Need help with my SoC proposal.
Hello, I just created a post on django-gsoc mailing list asking for help for preparing a proposal. Here is the link: http://groups.google.com/group/django-gsoc/browse_thread/thread/c920d7d3a29de727 I'd appreciate any help at this stage as I am quite confused about what to do next. Thank you. Fırat -- 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: Need help with my SoC proposal.
I decided to put the message itself here so you won't have to follow the link to another mailing list. Hello, I am a CS student from Turkey. I want to apply for Django's GSoC program this year. I have some ideas but am quite confused regarding what to propose. I want to give some information about myself so someone more experienced can point me in the right direction. I have been working on several Django projects for more than 2 years. I am one of the senior developers who built the largest Django based website in Turkey: http://markafoni.com (http:// www.brandsexclusive.com.au/a/aboutus/ for Australian version) . It is a clone of http://vente-privee.com, a private online shopping site. Markafoni ships more than 1000 items per day and the traffic is enormous. The system runs on several application servers, 2 db servers and a gateway. There are also several servers for backup. I have experience with almost every aspect of Django: scaling problems, writing complex widgets and forms, middlewares, context processors, etc. Because of my course load, I had to quit Markafoni last year, since it was getting very demanding for me. Right now, I am working part- time at my university as a member of the web-team. I managed to convince my co-workers to convert all the websites within the university to be built with Django and they are happier than ever. This year I have taken two courses that I like the best in my entire college life: SICP and PLAI. These courses teach and help us analyze structure of programming languages and paradigms, compilers, interpreters, etc (http://en.wikipedia.org/wiki/ Structure_and_Interpretation_of_Computer_Programs - http://en.wikipedia.org/wiki/PLAI). PLAI is, basically, a course where we keep improving a very basic interpreter that we write at the begging of the semester. I was the top of class in SICP and PLAI is still ongoing at the moment. But I think the results will be the same for PLAI. That's why I believe working on template compilation [http://code.djangoproject.com/wiki/ SummerOfCode2010#Templatecompilation] idea proposed on the SoC page would be a good choice for me. Should I devote myself to designing a solution for this problem or would you suggest I take a look at others? That's all I can think of right now. I'd appreciate some feedback. Thank you. Fırat -- 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.
Housekeeping ; GSoC 2010
Hello, My name is Zubin Mithra and I am a Python developer. I have considerable experience working with django but have no knowledge of its internal workings; however I would like to have GSoC 2010 as an opportunity to do the same. I am interested in the "Housekeeping" project idea which has been proposed as I have the necessary expertise for the same and can take this as an opportunity to understand django better. I have been through the various categories of tickets and have found tickets of the following categories in large numbers:- 1. django.contrib.admin 2. Database layer 3. Core Framework 4. Contrib apps Tickets from the any of the above mentioned sections could also be fixed as part of the project. As for previous open-source experiences, my recent contributions include integration of a keyring module into distutils2, a GeoLocator module for sahana-py and a few bug fixes at cobbler and transifex(which uses django). I would love to take part in GSoC with django as my mentoring organization. I would like any inputs I could use so that I could write a better proposal. Zubin Mithra http://zubin71.wordpress.com -- 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: Housekeeping ; GSoC 2010
On Tue, Mar 23, 2010 at 7:42 AM, zubin71 wrote: > Hello, > > My name is Zubin Mithra and I am a Python developer. I have > considerable experience working with django but have no knowledge of > its internal workings; however I would like to have GSoC 2010 as an > opportunity to do the same. I am interested in the "Housekeeping" > project idea which has been proposed as I have the necessary expertise > for the same and can take this as an opportunity to understand django > better. > > I have been through the various categories of tickets and have found > tickets of the following categories in large numbers:- > 1. django.contrib.admin > 2. Database layer > 3. Core Framework > 4. Contrib apps > > Tickets from the any of the above mentioned sections could also be > fixed as part of the project. > > As for previous open-source experiences, my recent contributions > include integration of a keyring module into distutils2, a GeoLocator > module for sahana-py and a few bug fixes at cobbler and > transifex(which uses django). > > I would love to take part in GSoC with django as my mentoring > organization. I would like any inputs I could use so that I could > write a better proposal. Based on what you've told us so far, the most important suggestion I can give you is "be specific". We are well aware that there are many open tickets in the areas you indicate, but we're not going to approve a project that reads "I'm going to fix tickets". The housekeeping proposal is a bit of a catch-all, and it's entirely possible that we might accept multiple students under the 'housekeeping' banner (e.g., housekeeping admin, housekeeping ORM, etc). If you're going to make a proposal on this topic, you need to be specific about what it is you intend to look at, and what you hope to achieve. If you're going to take a ticket-based approach, we'd like to see some sort of direction or plan in the tickets you hope to address. For example, last year we accepted a project about WSGI improvements; that project proposal listed over a dozen non-trivial WSGI specific tickets that needed to be addressed. A successful ticket-based application for the housekeeping task would need to propose a similar list of tickets. The "foreign key/m2m cleanup" suggestion on the SoC wiki is one such area - I suspect that closer inspection of the ticket system will reveal several tickets that are directly related to the internal complexity of the fk/m2m descriptors. The other approach is to pick an area (or areas) that requires some housekeeping activity, but aren't directly related to existing tickets. The "_meta" and "optimization" suggestions on the SOC page are these sorts of ideas. Saying _meta needs to be formalized isn't an issue that spawns multiple tickets. Optimization is one of those general tasks that can always be improved, so there aren't any tickets for that. There are other areas that may need some housekeeping attention of this sort, independent of any specific ticket activity. So - be specific. The more detail you give us, the more evidence you provide that you've looked into the problem in detail. The more evidence you can provide that you understand the problem, the more likely it is that you will be accepted. Yours, Russ Magee %-) -- 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.
Proposal - ChoiceField.choices need to accept callable, not only list or tuple
Hi, The subject pretty much describes all of it. If 'initial' can be a callable, why 'choices' can't? Writing custom function is way more convenient then altering __init__ method of the model. I'm happy to write up a patch if it would be likely to be accepted -- 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: Proposal - ChoiceField.choices need to accept callable, not only list or tuple
I say go for it, and post again with a patch and issue number (once you've created them). Your idea seems sound. Jared On Mon, Mar 22, 2010 at 11:30 PM, George Karpenkov wrote: > Hi, > > The subject pretty much describes all of it. If 'initial' can be a > callable, why 'choices' can't? Writing custom function is way more > convenient then altering __init__ method of the model. > > I'm happy to write up a patch if it would be likely to be accepted > > -- > 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. > > -- 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: Proposal - ChoiceField.choices need to accept callable, not only list or tuple
http://code.djangoproject.com/ticket/13181 On Mar 23, 4:42 pm, Jared Forsyth wrote: > I say go for it, and post again with a patch and issue number (once you've > created them). Your idea seems sound. > > Jared > > On Mon, Mar 22, 2010 at 11:30 PM, George Karpenkov > wrote: > > > > > Hi, > > > The subject pretty much describes all of it. If 'initial' can be a > > callable, why 'choices' can't? Writing custom function is way more > > convenient then altering __init__ method of the model. > > > I'm happy to write up a patch if it would be likely to be accepted > > > -- > > 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 > i...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/django-developers?hl=en. -- 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: Proposal - hook to modify links in object-tools
once again, I'm happy to write a patch if people think it's a good idea On Mar 11, 5:21 pm, George Karpenkov wrote: > Currently to add a link to object-tools one has to modify a template. > > I think that in most cases it would be much easier to do that through > python - if admin actions have a mechanism for removing existing ones/ > adding new ones why object-tools does not? > > Sometimes it's impossible to modify an admin template - ie providing > an admin mixin -- 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.
