The '-U' command line option has no config-based equivalent.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
I'd like for buildout.cfg to be able to indicate that the user's ~/.buildout/
For symmetry, I think that '-u' should be added as a command line option which indicates the user's default.cfg *SHOULD* be used. This (like '-U') would override any related setting in the config. But in the absence of either '-U' or '-u', the presence in the config of a keyword such as 'userdefaults' (userdefaults=
As an added bonus, '-U' and '-u' would adhere to the ad hoc convention of the uppercase letter argument being the negative setting and the lowercase letter argument being the positive setting. Furthermore, the default buildout behavior (if no command line argument is present and no config variable is provided) would continue to be 'use the default.cfg', so any existing scripts and such would continue working normally.
Changed in zc.buildout: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Of course, this isn't a bug, but a feature request. Patches,
including tests, accepted. :)
Jim
On Tue, Aug 4, 2009 at 3:43 PM, David Hostetler<email address hidden> wrote: default. cfg should not be used, but there is no keyword [true,false] ) would provide the /bugs.launchpad .net/bugs/ 409009
> Public bug reported:
>
> I'd like for buildout.cfg to be able to indicate that the user's
> ~/.buildout/
> associated with this option, there is only the '-U' command line option.
>
> For symmetry, I think that '-u' should be added as a command line option
> which indicates the user's default.cfg *SHOULD* be used. This (like
> '-U') would override any related setting in the config. But in the
> absence of either '-U' or '-u', the presence in the config of a keyword
> such as 'userdefaults' (userdefaults=
> authoritative value for that option.
>
> As an added bonus, '-U' and '-u' would adhere to the ad hoc convention
> of the uppercase letter argument being the negative setting and the
> lowercase letter argument being the positive setting. Furthermore, the
> default buildout behavior (if no command line argument is present and no
> config variable is provided) would continue to be 'use the default.cfg',
> so any existing scripts and such would continue working normally.
>
> ** Affects: zc.buildout
> Importance: Undecided
> Status: New
>
> --
> The '-U' command line option has no config-based equivalent.
> https:/
> You received this bug notification because you are subscribed to
> Buildout.
>
--
Jim Fulton