better messages about bad plugin names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Low
|
Dan Watkins |
Bug Description
"Wichmann, Mats D" <email address hidden>
to bazaar
show details
3:53 am (1 hour ago)
My first look at 0.15 wasn't terribly positive...
Unable to load plugin 'bzr-tags' from '/home/
is not a valid python module name.
Unable to load plugin 'bzr-gtk' from '/home/
not a valid python module name.
Unable to load plugin 'pqm-submit' from '/home/
is not a valid python module name.
Unable to load plugin 'update-mirrors' from
'/home/
The other plugins in my home directory are not
saying this.
What's up with this?
> >> I'm expecting people will go to the plugins page, do the
> >> branch using the link provided, and then get funky errors.
> >> Should plugin authors be renaming stuff now?
I think you're right. So what could we do to make this more obvious?
Really the 0.15 NEWS should have mentioned this under the heading of
'NOTES WHEN UPGRADING'; in the shipped version it does describe this
but not in a way that would let users understand why it broke or what
should have been done. For any change we should consider whether it
should be mentioned in NEWS and how - what the consequences to users
are.
* Allow 'import bzrlib.
yet been loaded by load_plugins(). This allows plugins to depend on each
other for code reuse without requiring users to perform file-renaming
gymnastics. (Robert Collins)
However that's moot because most users don't read most documentation. :-)
It would be better if the error said something like
Can't load ~/.bazaar/
a valid module name; try renaming it to bzr_gtk
through a simple substitution.
> There is also the fact that you wouldn't usually name the trunk/mainline
> as the project name. (for example
> http://
> )
>
> Because of this, the recommended way of branching is to always supply a
> target name. Otherwise you would end up with 10 'trunk' projects.
Maybe that page should give the whole command you need to use to install it?
bzr branch http://
Or we could have an install-plugin command as shorthand...
Related branches
Changed in bzr: | |
assignee: | nobody → daniel-thewatkins |
status: | Triaged → In Progress |
Still current in 0.91dev.