On Thu, Aug 27, 2009 at 2:03 PM, Justin Lilly wrote:
> Hey guys.
>
> I started writing some docs for another developer today and hit a few
> issues with admindocs that I plan on sprinting on for DjangoCon. I'm
> hoping anyone else with complaints / ideas will voice up, though my main
> impetus f
On Mon, Apr 19, 2010 at 8:19 AM, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> I'd like to try to reboot the discussion that's been going on about
> Django's development process.
>
> I'm finding the current thread incredibly demoralizing: there's a
> bunch of frustration being expressed, and I hear t
On Thu, Jun 10, 2010 at 11:21 AM, Andrew Godwin wrote:
> Hi all,
>
> I noticed today that the tutorial still does imports like "from
> mysite.polls.models import Poll", and URLs like "(r'^polls/$',
> 'mysite.polls.views.index')".
>
> At least in the places and projects I've worked with, the standa
On Fri, Jun 11, 2010 at 9:16 AM, Andrew Godwin wrote:
>
>
> On 11/06/2010 03:28, Peter Baumgartner wrote:
>>
>> In my experience, almost every project has domain-specific
>> applications that don't get reused. If you have a reusable app, you
>> bundle it sepa
Hi all! I'd like to re-open the discussion around
https://code.djangoproject.com/ticket/21978
As a "batteries included" framework, Django kind of leaves people to
fend for themselves when it comes to deployment. This makes it harder
than necessary for a developer to go from works-on-my-laptop to
w
t; INSTALLED_APPS doesn't seem too much to ask (I think.)
>
> Was it really 4 years ago Tom left that comment on #21978 😳 (We'd finally
> close this as wontfix: Django doesn't ship a webserver.)
>
> Does that fit in your view, or would that scenario not be good eno
ar up...)
>>
>> I think all these thoughts are really pursuable outside of core in the
>> very short run, even if the goal is to merge them — it's much easier to
>> experiment that way, and then say, "This worked".
>>
>> Anyhow, other than a "I&
I think is related here. (That's on my list too: async this QTR, then
>>>> hoping to take on Adam's proposal to modernise the Request object for the
>>>> end of year, then 🤞 swinging back here for "OK, what does it look like,
>>>> what can we do?
project template,
>>>> which I think is related here. (That's on my list too: async this QTR, then
>>>> hoping to take on Adam's proposal to modernise the Request object for the
>>>> end of year, then 🤞 swinging back here for "OK, what does it look l
On Sat, Oct 29, 2022 at 10:06 AM Peter Baumgartner
wrote:
> Thanks for the thorough review Florian! Some comments inline...
>
> On Wed, Oct 26, 2022 at 1:30 AM Florian Apolloner
> wrote:
>
>> Hi Pete,
>>
>> this does look interesting. And I agree that this is s
de):
>
> "We’ve included this with Django so you can develop things rapidly,
> without having to deal with configuring a production server – such as
> Apache – until you’re ready for production."
>
> https://docs.djangoproject.com/en/4.1/intro/tutorial01/
>
&
On Sun, Oct 30, 2022 at 7:57 AM Florian Apolloner
wrote:
> Hi Peter,
>
> On Saturday, October 29, 2022 at 6:07:16 PM UTC+2 pe...@lincolnloop.com
> wrote:
>
>> Since you asked for feedback, I'll tell you what I'd do differently (and
>>> this is also a sign that production environment vary widely).
On Mon, Oct 31, 2022 at 11:52 AM Florian Apolloner
wrote:
> On Monday, October 31, 2022 at 5:27:02 PM UTC+1 pe...@lincolnloop.com
> wrote:
>
>> In my ideal scenario, the default is a hard-coded settings file for the
>> project (deprecating DJANGO_SETTINGS_MODULE env var) and we have
>> CONFIG_LOA
It just moved. See:
http://code.djangoproject.com/browser/django/trunk/django/forms/fields.py#L924
http://code.djangoproject.com/browser/django/trunk/django/core/validators.py#L122
-- Pete
On Tue, Oct 12, 2010 at 8:44 AM, Sebastian wrote:
> Hello,
> I investigated a bit further, it was commited
On Thu, Nov 4, 2010 at 5:37 AM, silent1mezzo wrote:
> +1 for {% include "foo.html" x=1 y=2 %}
>
> This just seems more natural. My designer agreed based on the {% url
> %} tags.
>
+1 for using the = syntax here. My reasons have been mentioned above,
but to recap:
* and/as gets too verbose and d
You might find https://github.com/lincolnloop/goodconf interesting. I
see some overlap there with what you're doing.
On Mon, Mar 23, 2020 at 9:43 AM Abhirav Dilip Kariya
wrote:
>
> Hi,
>
> Thank your for the suggestion.
>
> I did look at some libraries. However, the libraries I looked into (or
I implemented something for this in the django-alive package via a
middleware that will bypass the host checking:
https://github.com/lincolnloop/django-alive/#disabling-allowed_hosts-for-healthchecks
https://github.com/lincolnloop/django-alive/blob/master/django_alive/middleware.py
On Fri, Sep 14
I'm interested in using PyOxidizer [1] to create single-file executable
Django projects. This currently isn't possible because of all the places
Django assumes it is operating on a proper filesystem. I haven't done a
full audit, but templates, migrations, and static files come to mind.
Python h
doesn't seem like that far fetched.
>>
>> Similarly for Django's migration files. Swapping out the MigrationLoader
>> would already be sufficient.
>>
>> I'd definitely be interested to see what's needed to change in core to have
>> a 3rd party packag
T if I'm not mistaking. Turning them into Python modules that a
>> >> new Jinja2ModuleTemplateLoader could load doesn't seem like that far
>> >> fetched.
>> >>
>> >> Similarly for Django's migration files. Swapping out the Migratio
It looks like there are some other fixes in 1.9 that weren't covered
by my monkeypatch. I upgraded the project and included a new cProfile
in the ticket https://code.djangoproject.com/ticket/22608#comment:23.
It shaved 100s off, but still takes 2.5 minutes to create an empty
migration.
Florian, I'
Reporting back on some additional findings for what it's worth.
SmileyChris dumped and recreated the project in question's migrations,
manually ordering them to minimize dependencies. It was not a major
reduction in total migrations: 82 to 58 (mostly third-party migrations
and initials), but the ti
If any of you keep an eye on this list, give me a shout. I may be on
the Front Range this weekend and would like to participate.
--
Pete
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
Can somebody take a look at
http://code.djangoproject.com/attachment/ticket/5247/
I updated the existing patch to work with current svn, but I'm not
familiar enough with the internals to be sure it isn't breaking things
elsewhere.
Thanks!
--
Pete
--~--~-~--~~~---~-
>
> I've done so rather briefly, comments on the ticket.
>
Ugh, I think I was asleep at the wheel there.
I've uploaded a better patch. If you have time, please take a look.
http://code.djangoproject.com/ticket/5247
Thanks!
--
Pete
--~--~-~--~~~---~--~~
You rec
http://code.djangoproject.com/ticket/3511 broke some code I had that
caught AssertionError in the past. Seems like it should be listed on
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
--
Pete
--~--~-~--~~~---~--~~
You received this message becau
26 matches
Mail list logo
