>> It's tricky.
>>
>> Ideally, you need to take your large code base, and reduce it into a
>> short piece of sample code that is runnable and reproduces your issue.
>
>
> +1 on this.
>
> There is no good answer. Speaking for myself, I would prefer that you
> attach the file to your email. But
On Sat, Sep 22, 2012 at 5:13 AM, Dwight Hutto wrote:
>
> I'd say youtube, but you couldn't copy and paste from the video, just
> look at the errors outputed, and a good long video of the code.
OK, but please don't make a video and basically grunt like Animal from
the Muppet Show: see code! see co
i have an assignment from a book to practice implementing relative
imports. it gave a very clear and easy to follow explanation, but my
results are proving the instructions are wrong. here's what i have
tried. my folder structure:
Project /
__init__.py
main.py
Domestic /
__init__
On 22/09/12 20:56, Matthew Ngaha wrote:
i have an assignment from a book to practice implementing relative
imports. it gave a very clear and easy to follow explanation, but my
results are proving the instructions are wrong.
Not impossible, but I doubt that.
Have you followed the instructions
Matthew Ngaha wrote:
> i have an assignment from a book to practice implementing relative
> imports. it gave a very clear and easy to follow explanation, but my
> results are proving the instructions are wrong. here's what i have
> tried. my folder structure:
>
> Project /
>
>__init__.py
>
> Not impossible, but I doubt that.
>
> Have you followed the instructions *exactly*? If not, you have
> probably missed something. What book is it?
>
> Otherwise, the book and you are probably using different versions of
> Python. What version of Python are you using, and what is the book
> using?
> You probably have a path that reaches into Domestic or Europe sub-package.
> That can happen if e. g. Project/Domestic/Europe is your current working
> directory.
>
> Try to cd into the Project folder's parent directory and see if
>
> $ python -c 'import Project.Domestic.Europe.winners'
>
> works
On 09/22/2012 08:33 AM, Matthew Ngaha wrote:
>> You probably have a path that reaches into Domestic or Europe sub-package.
>> That can happen if e. g. Project/Domestic/Europe is your current working
>> directory.
>>
>> Try to cd into the Project folder's parent directory and see if
>>
>> $ python -
On Sat, Sep 22, 2012 at 12:25 AM, Muse Gk wrote:
>
> I had tried MinGW-w64 today, however, another more errors happen which
> just like this (
> http://stackoverflow.com/questions/6034390/compiling-with-cython-and-mingw-produces-gcc-error-unrecognized-command-line-o
> ). Another no solution error.
> try
> import ../my_module
> instead of
> import ..my_module
> and see what happens.
> Your problem may be just that you haven't included the separator.
>
> .. means one directory higher but you must separate it from the file name.
>
> Two directories higher would be
> ../../my_module
sadly this
> cd is a shell command; you do it before starting Python. You didn't
> mention what OS you're running, but cd should be about the same for
> Linux, Windows, or Mac.
im on windows. i always start Python via IDLE. ive never started it
for editing though the shell, run > cmd etc? ill type that int
>On 21/09/12 20:51, Albert-Jan Roskam wrote:
>> Hi,
>>
>> My company just started application whitelisting. Now a new version of
>>a (benign!!) dll does not work as it (or rather, its file hash, if I
>>understood it correctly) is not whitelisted.
>
>Then get it whitelisted. If your company does
> You probably have a path that reaches into Domestic or Europe sub-package.
> That can happen if e. g. Project/Domestic/Europe is your current working
> directory.
>
> Try to cd into the Project folder's parent directory and see if
>
> $ python -c 'import Project.Domestic.Europe.winners'
>
> works
eryksun (),
I really appreciate what you had done for me.
I still can not make through those errors. Or I can say there is no
way install pycrypto with MinGW or Cygwin.
>Also, according to http://bugs.python.org/issue4709, you might need
>MS_WIN64 to be manually defined. Try installing like this
Matthew Ngaha wrote:
>> You probably have a path that reaches into Domestic or Europe
>> sub-package. That can happen if e. g. Project/Domestic/Europe is your
>> current working directory.
>>
>> Try to cd into the Project folder's parent directory and see if
>>
>> $ python -c 'import Project.Domes
> You had forward slashes in your description of the folder layout, so I
> assumed you were on a linux box or a mac. I think I have now learned the
> lesson and will make fewer assumptions in the future.
>
> First, in idle's "shell" window type
>
import sys
print(sys.executable)
>
> (dont
On Sat, Sep 22, 2012 at 11:25 AM, Muse Gk wrote:
>
> c:/users/gk/downloads/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.5.4/../../../.
> ./x86_64-w64-mingw32/bin/ld.exe: skipping incompatible
> C:\Python27\libs/libpytho
> n27.a when searching for -lpython27
FYI, -lpython27 is for linking to the p
Hi,
On 22 September 2012 11:56, Matthew Ngaha wrote:
> from ..silverware import Silverware
> heres my error mesages: ... ValueError: Attempted relative import in
> non-package
Just an off the cuff remark since no one else picked up on this, but
the above errir message to me implies there's poss
18 matches
Mail list logo