Re: Cleaning up manage.py and import paths

This is fantastically clear and sensible. +1. I can't count the hours I've lost either chasing PYTHONPATH issues or helping nontechnical people work around them so they could deploy their newly-minted thing. I -- You received this message because you are subscribed to the Google Groups

Re: Cleaning up manage.py and import paths

On Oct 12, 9:31 am, Idan Gazit wrote: > This is fantastically clear and sensible. +1. > > I can't count the hours I've lost either chasing PYTHONPATH issues or > helping nontechnical people work around them so they could deploy their > newly-minted thing. I would agree that this

Re: Update on Ticket #16891: Delete/update should return number of rows modified

Uhm question -- Does the count for Model.save() make any sense? Isn't that always one? Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

#16869 - BaseGenericInlineFormSet does not use form's save() method

Hello, As described on the ticket [1], I attach a patch that changes the behaviour of "save_new" method in order to use the form's "save" method. Is the patch correct, or there's something to improve? Thanks in advance [1] https://code.djangoproject.com/ticket/16869 [2]

#17028 - diveintopython.org links now dead

Hello, As described on the ticket [1], it seems that diveintopython.org is dead, so I changed every occurence for the mirror http://diveintopython.nfshost.com/, that it seems to be the most updated. The changes are on the patch attached in the ticket [2]. Best regards [1]

Re: #17028 - diveintopython.org links now dead

How about: http://web.archive.org/web/20110726001211/http://diveintopython.org/ ? On Wed, Oct 12, 2011 at 2:37 AM, rikuthero...@gmail.com wrote: > Hello, > > As described on the ticket [1], it seems that diveintopython.org is dead, so > I changed every occurence for  the

Re: #17028 - diveintopython.org links now dead

Both have the content updated since 20 May 2004, so the content it's the same, and I think is better to have a smaller URL, and it has no header banner like the one from web.archive.org But as I said, the content is really the same, so there should be no problem changing it. 2011/10/12 Jeremy

Re: #17028 - diveintopython.org links now dead

Mirrors are appearing in a number of places for this and the html5 version. Its hard to know which are more likely to stick around. http://diveintopython3.ep.io/ https://github.com/diveintomark/diveintopython3 Dougal -- You received this message because you are subscribed to the Google

Re: #17028 - diveintopython.org links now dead

Those mirrors are from Dive into Python 3, is not the one linked from the Django docs. 2011/10/12 Dougal Matthews > Mirrors are appearing in a number of places for this and the html5 > version. Its hard to know which are more likely to stick around. > >

Re: Cleaning up manage.py and import paths

On Tue, Oct 11, 2011 at 6:05 AM, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > In the spirit of making Django behave better as a Python library (c.f. > Glyph's keynote at djangocon.us), I'd like to finally tackle removing > the sys.path

Re: Cleaning up manage.py and import paths

On Oct 11, 9:05 am, Carl Meyer wrote: > What's the impact on adding a standard WSGI entrypoint? > - --- > > #16360 [5] has a patch to add a "wsgi.py" file to the default project, > which will serve as a standard WSGI

Re: #17028 - diveintopython.org links now dead

On Wed, Oct 12, 2011 at 5:37 PM, rikuthero...@gmail.com wrote: > Hello, > > As described on the ticket [1], it seems that diveintopython.org is dead, so > I changed every occurence for  the mirror > http://diveintopython.nfshost.com/, that it seems to be the most updated.

Re: Cleaning up manage.py and import paths

I suggest naming it src, and then having example.com - contrib - docs - public - src - manage.py - myapp - __init__.py - settings.py - urls.py - virtualenv -- You received this message because you are subscribed to the

Re: #17028 - diveintopython.org links now dead

Hello, Sorry, it seems that I miss that last point. I'll try to re-read the contribution docs and work better in the proper way. Thanks and sorry again. 2011/10/12 Russell Keith-Magee > On Wed, Oct 12, 2011 at 5:37 PM, rikuthero...@gmail.com >

Towards a more friendly NoReverseMatch

It would be really good if we could improve the errors provided when Django can't do reverse(). For example: >>> reverse('i_dont_exist') NoReverseMatch: Reverse for 'i_dont_exist' with arguments '()' and keyword arguments '{}' not found. In this case, it would be nicer to have something

Re: Cleaning up manage.py and import paths

On Mon, Oct 10, 2011 at 3:05 PM, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 ... > 2. People write code that imports things inconsistently (sometimes with > the project prefix, sometimes without it), and then when they go to > deploy (without manage.py or

Re: Cleaning up manage.py and import paths

On Tue, Oct 11, 2011 at 9:05 AM, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > In the spirit of making Django behave better as a Python library (c.f. > Glyph's keynote at djangocon.us), I'd like to finally tackle removing > the sys.path

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Alec, On 10/12/2011 06:38 AM, Alec Taylor wrote: > Backwards compatibility is easily solved, include an upgrade.py file > which is called if project rootfolder has settings.py. upgrade.py > would fix the directory structure Thanks for the

Re: Update on Ticket #16891: Delete/update should return number of rows modified

On Oct 12, 1:37 pm, Johannes Dollinger wrote: > Ticket #12086 is a duplicate. I don't think QuerySet.delete() should return > the number of all collected objects, but just the number of objects deleted > from QuerySet.model. Agree. A way to get the counts per object

Re: Cleaning up manage.py and import paths

Moving the manage.py is a great move. Post 1.4 you actually might want to think a bit about integrating a distutils2 setup.cfg into the manage.py folder and the startproject command. Since distutils2 will be the standard in python3.3 for packaging and backported to python 2.5 it makes sense to

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Karen, On 10/11/2011 06:21 PM, Karen Tracey wrote: > One thing that I think should be added before commit is a note in the > tutorial along the lines of "what if startproject didn't actually do > what we are saying it did?" and explaining that the

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Russ, On 10/12/2011 05:14 AM, Russell Keith-Magee wrote: > My only feedback on the patch is a point of clarification in the > tutorial. Rather than creating a mysite directory with a mysite > project directory in it, and then having to refer to

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Graham, On 10/12/2011 05:16 AM, Graham Dumpleton wrote: > Apache/mod_wsgi does not change the current working directory to be > where the WSGI file is located so that will not work for Apache/ > mod_wsgi. A sys.path modification would still be

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mateusz, On 10/12/2011 05:20 AM, Mateusz Harasymczuk wrote: > I suggest naming it src, and then having > > example.com > - contrib > - docs > - public > - src > - manage.py > - myapp > - __init__.py >

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brett, On 10/12/2011 07:11 AM, Brett H wrote: > Post 1.4 you actually might want to think a bit about integrating a > distutils2 setup.cfg into the manage.py folder and the startproject > command. Oh, I certainly have thought about it :-) A

Re: Update on Ticket #16891: Delete/update should return number of rows modified

It is for now, but the ticket I'm building up to [1] is that it may actually be 0 if a precondition is not met. This is how your code can know if the current request really got to do a save or delete if two or more are trying to update the object at the same time. [1]

Re: Update on Ticket #16891: Delete/update should return number of rows modified

-- Steven On Wed, Oct 12, 2011 at 5:37 AM, Johannes Dollinger wrote: > > Am 12.10.2011 um 03:35 schrieb Steven Cummings: > > Ticket #12086 is a duplicate. I don't think QuerySet.delete() should return > the number of all collected objects, but just the number of

Re: Update on Ticket #16891: Delete/update should return number of rows modified

-- Steven On Wed, Oct 12, 2011 at 8:07 AM, Anssi Kääriäinen wrote: > > Model.save() should return models.UPDATED or models.INSERTED. That is > more helpful than the 1/0 return value. For example you might want to > do different things if the model was inserted or

Re: Cleaning up manage.py and import paths

On Wed, Oct 12, 2011 at 9:23 PM, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Russ, > > On 10/12/2011 05:14 AM, Russell Keith-Magee wrote: >> My only feedback on the patch is a point of clarification in the >> tutorial. Rather than creating a mysite

Re: Towards a more friendly NoReverseMatch

On Wed, Oct 12, 2011 at 12:56 PM, Wilfred Hughes wrote: > It would be really good if we could improve the errors provided when > Django can't do reverse(). > > For example: > >    >>> reverse('i_dont_exist') >    NoReverseMatch: Reverse for 'i_dont_exist' with arguments

Re: Update on Ticket #16891: Delete/update should return number of rows modified

On Oct 12, 4:47 pm, Steven Cummings wrote: > If you're ensuring a set of data from some other source, what's the use of > knowing what was new? Are there other concrete cases where this might be > useful? The standard use when synchronizing data is to make sure there aren't

Re: Cleaning up manage.py and import paths

On 12/10/11 15:06, Carl Meyer wrote: > > > On 10/12/2011 07:53 AM, Russell Keith-Magee wrote: >> I'm not convinced it's a bad idea. From an pedagogical perspective, >> it's easy to explain -- Make a directory to contain all the bits for >> your project, move into the directory, then bootstrap

Re: Cleaning up manage.py and import paths

+1 mkdir project cd project git init django-admin.py startproject project Is basically what I already do, and either way it's not terrible hard to switch, but I think it makes a lot of sense to use CWD as the top level directory. On Wednesday, October 12, 2011 at 10:59 AM, Luke Plant

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Luke, On 10/12/2011 08:59 AM, Luke Plant wrote: >> It's not so easy to explain why startproject can't just create the >> directory to contain all the bits it creates in the first place, instead >> of making me do it manually :-) > > I think there

Re: Cleaning up manage.py and import paths

Hmm, well maybe we need to survey current structures, I'd expect some constant (i.e. the settings.py file) On Wed, Oct 12, 2011 at 11:53 PM, Carl Meyer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Alec, > > On 10/12/2011 06:38 AM, Alec Taylor wrote: >>

Re: Towards a more friendly NoReverseMatch

> >    >>> reverse('i_dont_exist') > >    NoReverseMatch: Reverse for 'i_dont_exist' with arguments '()' and > > keyword arguments '{}' not found. > > > In this case, it would be nicer to have something like: > > >    NoURLPattern: No patterns specified for 'i_dont_exist'. > > Just on this point,

Re: Cleaning up manage.py and import paths

Carl, why not have django-admin.py startproject create a site_root directory and within it a project_root directory by default if issued from within e.g. example.com (the outermost container/directory e.g. a virtualenv): example.com <-- mkvirtualenv example.com; non-Python stuff somehow

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Markus, On 10/12/2011 10:30 AM, Markus Gattol wrote: > django-admin.py startproject would create site_root and project_root > put as this patch intends, one could always easily rename site_root to > whatever he wants. example.com is entirely

Re: Cleaning up manage.py and import paths

On Oct 12, 7:59 am, Luke Plant wrote: >  $ mkdir foo >  $ cd foo >  $ hg init > >  # OK, now what am I going to put in it? Oh, a Django project. > > In fact, it might be good idea to encourage use of VCS by mentioning it. > If I remember SVN correctly, you would actually

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Chris, On 10/12/2011 05:28 PM, Chris Beaven wrote: > Great job on getting the ball rolling on this, Carl! > > +1 on the whole idea Thanks! > Similar to what Russ and Luke are saying, I'd also prefer it if > startproject dropped manage.py and

Re: Cleaning up manage.py and import paths

+1 on installing CWD. Integrates nicely with the virtualenvwrapper mkproject command. I have a much longer reasoning why startproject should not get into creating the outer folder which is effectively the distribution folder, and the domain of distribution packaging tools, so I'll follow this

Re: RFC: "universal" view decorators

Definitely +1 on this idea. It seems to me like the cleanest solution yet proposed insofar as it provides the desired new functionality while requiring very little change for current code. Cheers, AT On Wed, Oct 12, 2011 at 5:31 PM, Donald Stufft wrote: > Sorry for the

Re: Cleaning up manage.py and import paths

On 13/10/11 01:09, Carl Meyer wrote: >> Similar to what Russ and Luke are saying, I'd also prefer it if >> startproject dropped manage.py and the project Python package in the >> current working directory (with overwrite checks first). > > I remain -1 on CWD pollution by default; I haven't yet

Re: Cleaning up manage.py and import paths

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brett, On 10/12/2011 06:31 PM, Brett H wrote: > Having reworked project structures so many times I think creating the > outer folder 'site_root' with startproject is a bad idea. Making > startproject install manage.py in the current working

Re: Update on Ticket #16891: Delete/update should return number of rows modified

On Oct 13, 5:40 am, Steven Cummings wrote: [About the 1/0 return value of .save()] > Well, obviously I hope it does have use in the original ticket that spawned > this one. I guess what I might need some help with here is: what are some of > the directions of the ORM that

Re: Update on Ticket #16891: Delete/update should return number of rows modified

On Wed, Oct 12, 2011 at 11:51 PM, Anssi Kääriäinen wrote: > > > My point is that we should never just return 0 if there is a > concurrent modification or some other reason for not being able to > persist the object state. Why? When you request obj.save() you are >