On 4/26/2018 4:22 PM, Serhiy Storchaka wrote:
What syntax errors did you see most often? Which of them looks the most
weird? How would you like to improve their messages.
One way to research this would be to search stackoverflow.com for
"[python] SyntaxError". There are currently 8142 results
On 26 April 2018 at 21:18, Terry Reedy wrote:
>> If my memory is correct, this is the default for path directories.
>
> The Python entries do, as added by the Windows Installer written by a
> Microsoft engineer, so this must at least be a correct alternative.
It's definitely acceptable - there's
What syntax errors did you see most often? Which of them looks the most
weird? How would you like to improve their messages.
--
https://mail.python.org/mailman/listinfo/python-list
On 4/26/2018 3:04 PM, Virgil Stokes wrote:
However, each entry in this Windows 10 path has a trailing backslash.
Some do, and some don't, which is the same on my Win10
If my memory is correct, this is the default for path directories.
The Python entries do, as added by the Windows Installe
On 26 April 2018 at 20:04, Virgil Stokes wrote:
> IMHO it would have been useful to have "warning" somewhere in these
> messages.
Ha, I'd never even noticed that it didn't...
I think it's in a different colour, FWIW, but your point is good.
Paul
--
https://mail.python.org/mailman/listinfo/pytho
Thanks Paul for the prompt reply,
However, each entry in this Windows 10 path has a trailing backslash. If
my memory is correct, this is the default for path directories.
IMHO it would have been useful to have "warning" somewhere in these
messages.
On 2018-04-26 20:52, Paul Moore wrote:
On
On 26 April 2018 at 19:33, Virgil Stokes wrote:
> Why am I getting this message, that I need to consider adding this directory
> to PATH when it is already in PATH?
> Note, all of these *.exe files are in C:\Python36\Scripts.
The PATH entry ends with a backslash, which is confusing the check
done
First I upgraded my pip
*C:\Python36>python -m pip install --upgrade pip*
Collecting pip
Downloading
https://files.pythonhosted.org/packages/0f/74/ecd13431bcc456ed390b44c8a6e917c1820365cbebcb6a8974d1cd045ab4/pip-10.0.1-py2.py3-none-any.whl
(1.3MB)
100% ||
On 26/04/18 17:37, Skip Montanaro wrote:
> I'm going through a bout of RSI problems with my wrists, so klst night
> I refreshed an old typing watcher program I wrote a couple decades ago
> (there's a comment about Python 1.4 in the code!):
>
> https://github.com/smontanaro/python-bits/blob/master/
> Thanks, I do have that. Now to figure out when it changes state...
> Unfortunately, the timestamp on the file seems to update continuously,
> not just on state changes. Maybe /proc/acpi/wakeup will be of some
> use.
It appears that I can, at least some of the time. Might need to check
it more fr
> No idea if it'll work on your system, but on my laptop, there's a
> pseudo-file /proc/acpi/button/lid/LID0/state that has whether the lid
> is open or closed.
Thanks, I do have that. Now to figure out when it changes state...
Unfortunately, the timestamp on the file seems to update continuously,
On Wed, 25 Apr 2018 14:32:01 -0700, Sayth Renshaw wrote:
> Hi
>
> Hoping for guidance trying to find some advanced articles or guides or
> topics for json parsing.
>
> I can parse and extract json just dandy.
>
> What I am trying to figure out is how I give myself surety that the data
> I parse
On Fri, Apr 27, 2018 at 1:37 AM, Skip Montanaro
wrote:
> I'm going through a bout of RSI problems with my wrists, so klst night
> I refreshed an old typing watcher program I wrote a couple decades ago
> (there's a comment about Python 1.4 in the code!):
>
> https://github.com/smontanaro/python-bit
I'm going through a bout of RSI problems with my wrists, so klst night
I refreshed an old typing watcher program I wrote a couple decades ago
(there's a comment about Python 1.4 in the code!):
https://github.com/smontanaro/python-bits/blob/master/watch.py
It's far from perfect and I'm sure miles
tart...@gmail.com writes:
> On Wednesday, April 18, 2018 at 1:59:14 AM UTC-5, Cecil Westerhof wrote:
>> After I updated pip2/3 to 10 from 9 I sometimes get:
>> Cache entry deserialization failed, entry ignored
>>
>> For example when I execute:
>> pip3 list --outdated
>>
>> But not always
On Wednesday, April 18, 2018 at 1:59:14 AM UTC-5, Cecil Westerhof wrote:
> After I updated pip2/3 to 10 from 9 I sometimes get:
> Cache entry deserialization failed, entry ignored
>
> For example when I execute:
> pip3 list --outdated
>
> But not always.
>
> What could be happening here?
16 matches
Mail list logo
