Can't add an option called "name"

Bug #1351637 reported by Niko Coutsos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
configglue
New
Undecided
Unassigned

Bug Description

I kind of expected this, because the `Schema` class adds a property called `name` as well, but surprisingly I don't even have a way to avoid naming conflicts by calling my option property something else and giving it `name="name"` in the initializer.

The problem seems to come from this line:

http://bazaar.launchpad.net/~configglue/configglue/trunk/view/head:/configglue/schema.py#L141
(sorry, not sure how to link to the specific revision)

I think this should only set the option's name if it is not already set.

Revision history for this message
Niko Coutsos (ncoutsos) wrote :

I guess this kind of screws up a lot of things... even if I can get option.name = "name" other areas rely on being able to get the option attribute by its name matching the name of the attribute in the section.

Has this come up before?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.