On Tue, Oct 11, 2011 at 02:06, Luke Plant wrote:
> On 10/10/11 23:05, Carl Meyer wrote:
>
> > Unless there are significant objections, I'd like to commit this in the
> > next few days and get it into 1.4. I'll also modify the patch on #16360
> > to take advantage of the new layout; hopefully that
2011/10/11 Carl Meyer :
> Unless there are significant objections, I'd like to commit this in the
> next few days and get it into 1.4. I'll also modify the patch on #16360
> to take advantage of the new layout; hopefully that can get into 1.4 as
> well.
>
> Let me know if you see something I've ove
On 11 October 2011 02:06, Luke Plant wrote:
> On 10/10/11 23:05, Carl Meyer wrote:
>
>> Unless there are significant objections, I'd like to commit this in the
>> next few days and get it into 1.4. I'll also modify the patch on #16360
>> to take advantage of the new layout; hopefully that can get
Hello,
At the moment, the Django site doesn't provide any guidance about the
development tools (editors or IDEs) that can be used for developing Django
applications. There are already a number of IDEs with good Django support
(disclaimer: I'm the lead developer on one of them, namely PyCharm), and
On Tue, Oct 11, 2011 at 7:27 AM, Dmitry Jemerov wrote:
> I've discussed this with Russell Keith-Magee during DjangoCon.EU, and he
> seemed to be in favor of this. Does the community think that it's
> worthwhile? Is there anything specific we can do to get this moving?
>
> I can submit a proposed p
On Tue, Oct 11, 2011 at 9:21 AM, Jacob Kaplan-Moss wrote:
> On Tue, Oct 11, 2011 at 7:27 AM, Dmitry Jemerov
> wrote:
> > I've discussed this with Russell Keith-Magee during DjangoCon.EU, and he
> > seemed to be in favor of this. Does the community think that it's
> > worthwhile? Is there anything
2011/10/11 Alex Gaynor :
> I hate to use the "w" word, but this seems infinitely better as a wikipage.
I agree with Alex: I'd prefer if this information was community-managed.
A quick search turns up:
https://code.djangoproject.com/wiki/DjangoResources#Developmentenvironment
https://code.djangopr
Hello,
I think it's a great iniciative. It would be great to have something like
that. Maybe the perfect place is the wiki. IMHO something like the
DjangoFriendlyWebHosts [1] would be a good approach.
[1] https://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
On Tue, Oct 11, 2011 at 1:27 PM,
Hello Alex,
On Oct 11, 3:25 pm, Alex Gaynor wrote:
> I hate to use the "w" word, but this seems infinitely better as a wikipage.
> For one we avoid any appearance of endorsement (and given the diversity of
> options in this space, that's not a bad thing). Second, it allows for much
> more compr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi TiNo,
On 10/11/2011 06:10 AM, TiNo wrote:
> Definitely +1, as this has bitten me far too often. It would be nice
> however to also depend less on the ('hacky', as Glyph also noted)
> DJANGO_SETTINGS_MODULE environment variable. We shouldn't need an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2011 09:34 AM, Carl Meyer wrote:
> setup_environ, which will be deprecated). Instead, I expect wsgi.py will
> simply contain a line very similar to what is currently in manage.py,
> "os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'mysite.sett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Hanne,
On 10/11/2011 06:31 AM, Hanne Moa wrote:
> I already do it this way except the manage.py is vanilla.
>
> project-package/
> project.wsgi
> requirements.txt
> setup.py
> .git
> bin/ # virtualenv
> ...
> project/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Aymeric,
On 10/11/2011 06:12 AM, Aymeric Augustin wrote:
> The new structure highlights that a Django project is:
> - an entrypoint for scripts manage.py — and soon another one for WSGI servers,
> - a settings module and a root URLconf, who happen
> I think we should add a dedicated "Python path and project layout" page,
> and link to it from the tutorial and elsewhere. This gets way too
> complex to load onto beginners right away in the tutorial.
>
IIRC then this page has been proposed before and ultimately not been done
because the rati
Definitely in favor of removing it. I've run into that before and been
frustrated by hacking around the strange indentation.
- Gabriel
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Markus,
On 10/11/2011 11:50 AM, Markus Gattol wrote:
>
> I think we should add a dedicated "Python path and project layout" page,
> and link to it from the tutorial and elsewhere. This gets way too
> complex to load onto beginners righ
On Tue, Oct 11, 2011 at 3:50 PM, Carl Meyer wrote:
> After talking to Aymeric more on IRC, we agreed that this added docs
> page doesn't need to block the patch. The current documentation in the
> patch is adequate, this page would be an additional improvement. Which
> is good, because I'm not su
On 10/10/11 17:30, Jacob Kaplan-Moss wrote:
> Heh, so actually funny story.
>
> Turns out I copied this hack was over from the code I used for the
> Django book. We did it there to surpress a difference between the HTML
> conversion we used on the website and the OpenOffice conversion we
> used f
Finally got around to these simple changes:
*
https://github.com/estebistec/django/commit/b48a87afc324f5546b6654fa7638e406b397c0d6
*
https://github.com/estebistec/django/commit/28ace32980b370fd17ae35019bfe8d055c673684
If the core devs approve of these changes I can get to work on creating the
pro
19 matches
Mail list logo
