>
>
>
> Fabio Zadrozny-2 wrote:
> >
> > So, it is actually specifying the encoding in a way that should be
> > recognized as a valid encoding for the file (so, pydev correctly looks
> at
> > it
> > when trying to make parses). Looking at:
> > http://www.delorie.com/gnu/docs/emacs/emacs_220.html it
Fabio Zadrozny-2 wrote:
>
> Actually, the problem is the way in which the mode for emacs is
> specified...
> the encoding is specified as in PEP 0263 (
> http://www.python.org/dev/peps/pep-0263/), which pydev recognizes: match
> of
> the regexp coding[:=]\s*([-\w.]+)
>
Hey, thanks. I wasn't aw
On 8/7/07, patrimith <[EMAIL PROTECTED]> wrote:
>
>
> That comment line in Tix.py seems to be specifying information for Emacs
> python-mode. Is it?
>
> If so, should PyDev even be looking at this at all?
>
> I would venture to say that the warning should not be suppressed. If the
> Emacs specific
That comment line in Tix.py seems to be specifying information for Emacs
python-mode. Is it?
If so, should PyDev even be looking at this at all?
I would venture to say that the warning should not be suppressed. If the
Emacs specific settings are ignored entirely then the error won't happen in
t
>
>
> I am getting the following error in my eclipse 3.3 workspace log. It's
> understandable that my windows machine doesn't understand a unix encoding,
> but I've installed python 2.4.4 using the Windows *.msi from python.organd
> pydev 1.3.8 from the update site.
>
> Here's the error:
>
> !ENTRY
Hello List!
I am getting the following error in my eclipse 3.3 workspace log. It's
understandable that my windows machine doesn't understand a unix encoding,
but I've installed python 2.4.4 using the Windows *.msi from python.org and
pydev 1.3.8 from the update site.
Here's the error:
!ENTRY or
