On 11 June 2011 04:55, Pierre Thibault <pierre.thibau...@gmail.com> wrote: > 2011/6/9 Pierre Thibault <pierre.thibau...@gmail.com> >> >> 2011/6/9 <caleb.hatti...@gmail.com> >>> >>> On , Anthony <abasta...@gmail.com> wrote: >>> > Do you have an app to reproduce the problem? I created an app named >>> > "Castalia" (note the capitalization) with a module >>> > /modules/selfgroup/castalia/config.py, which I think is the same structure >>> > and naming as Alessandro's app. In a controller action, I then did: >>> > >>> > from selfgroup.castalia import config >>> > >>> > and it seems to work fine, though I believe Alessandro was getting an >>> > import error at that point. But maybe I'm missing something. >>> >>> I think we should ask him to make a small test app for us that >>> demonstrates the problem. Else we're guessing. >> >> Alessandro, can you send us the code having the unexpected behavior so the >> Windows guys can take a look? >> >> As I understand, you have to remove the capitalization to make it work >> because otherwise even if the capitalization match, it does not import >> properly. Right? >> >> -- > > OK, since we cannot reproduce the bug and we cannot know precisely what the > bug is, we will consider the issue closed. Do you think there is something > to add about this issue?
I would agree with that. Anthony has tested the capitalization issue directly (it works), and I checked what happens on Windows with capitalized nested folders and import statements (they work if the capitalization is matched). I think we need a reproducible test case here.
