#2590 closed bug (fixed)
Can't open Python console after new layer creation
| Reported by: | alexbruy | Owned by: | wonder |
|---|---|---|---|
| Priority: | major: does not work as expected | Milestone: | Version 1.5.0 |
| Component: | Python plugins and bindings | Version: | Trunk |
| Keywords: | python, console | Cc: | gislab, dr |
| Must Fix for Release: | No | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
To reproduce:
- create new empty shapefile with QGIS (point, polygon or line), add one attribute
- start editing and add few object to the layer
- save edits
- try to open Python console
- get error "Failed to open Python console: exceptions.NameError: name '_qgis_featureform_220100325194534055' is not defined"
Change History (8)
follow-up: 2 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Replying to wonder:
I believe this error is related to the usage of custom form for editing of feature attributes: a form fails to load and the python exception is set, but not handled until the python console is started. Can you confirm?
I don't use custom form for attributes editing. Also I disable "Open feature form, if a single feature identified" but error remains
Or it could be related to one of the plugins...
All plugins are unloaded and same result - error.
follow-up: 5 comment:3 by , 14 years ago
Still the problem occurs? I can't reproduce it and have no idea where's the reason.
comment:4 by , 14 years ago
I confirm, problem is still here. No forms, fresh nightly build, new project with only one layer in it. http://gis-lab.info/images/screenshots/20100617-f69-12kb.jpg
comment:6 by , 14 years ago
| Milestone: | Version 1.5.0 → Version 1.6.0 |
|---|---|
| Owner: | changed from to |
comment:7 by , 14 years ago
| Milestone: | Version 1.6.0 → Version 1.5.0 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Should be fixed in r13751.
Not reproducible here.
I believe this error is related to the usage of custom form for editing of feature attributes: a form fails to load and the python exception is set, but not handled until the python console is started. Can you confirm?
Or it could be related to one of the plugins...