grokproject does not like dotted names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grok |
Confirmed
|
Undecided
|
Brandon Rhodes | ||
1.0 |
Confirmed
|
Undecided
|
Martijn Faassen |
Bug Description
This refs http://
Oh well, I will paste that complete post.
maurits@hobb:~/grok $ grokproject one.two
Enter user (Name of an initial administrator user): admin
Enter passwd (Password for the initial administrator user): admin
Enter eggs_dir (Location where zc.buildout will look for and place packages) ['/home/
Creating directory ./one.two
Downloading zc.buildout...
Invoking zc.buildout...
Couldn't find index page for 'onetwo' (maybe misspelled?)
While:
Installing i18n.
Getting distribution for 'onetwo'.
Error: Couldn't find a distribution for 'onetwo'.
As you can see, this fails. Is this a known bug? Or should
grokprojects not have dots in them?
This can be fixed by:
- replacing all occurences in the generated code of onetwo with
one.two, except in app.py where "class one.two(...)" would give a
syntax errror
- turning src/onetwo into src/one/two (with a proper __init__.py
added)
Perhaps something I can look at on the Grokkerdam sprint with
someone? :)
Changed in grok: | |
assignee: | nobody → brandon-rhodes |
milestone: | none → 1.0 |
Changed in grok: | |
status: | New → Confirmed |
This looks like a great idea to me: that grokproject should be able to handle the creation of a package- in-a-namespace- package instead of users having to manually create a first-level grokproject and then move it beneath a namespace package themselves.
I'll ask the list about this.