On Thu, 17 Dec 2015 14:03:25 +0100, Siegfried Kaiser wrote:
> I have a problem with os.walk - it does not walk into a mounted cdrom, I
> do not see the cdrom in the walk at all.
> What can I do to walk into cdrom?
1. Are you sure that the directory tree contains the actual mount point,
not just
good explanation Steven but can you please do more by posting the exact code
as it relate to the question please?
--
https://mail.python.org/mailman/listinfo/python-list
On Sat, Dec 19, 2015 at 9:16 AM, Marko Rauhamaa wrote:
> Terry Reedy :
>
>> Guido also wants syntax chars and identifiers in stdlib code kept to
>> ascii only for universal readability.
>
> Readability, or writability? Most people would have no idea how to
> produce the characters with their keybo
Às 22:44 de 04-12-2015, Anna Szaharcsuk escreveu:
> Hello there,
>
> I was trying to install PyCharm, but didn't worked and needed interpreter.
> the computer advised to install the python for windows.
>
I don't know PyCharm but it is likely it needs python.
Did you install python?
You may need
Terry Reedy :
> Guido also wants syntax chars and identifiers in stdlib code kept to
> ascii only for universal readability.
Readability, or writability? Most people would have no idea how to
produce the characters with their keyboards.
Marko
--
https://mail.python.org/mailman/listinfo/python-
On 12/18/2015 4:49 AM, Steven D'Aprano wrote:
On Fri, 18 Dec 2015 05:51 pm, Chris Angelico wrote:
I would be inclined to ASCIIfy the apostrophes, dashes, and the
connection.py space that started this thread. People's names, URLs,
and demonstrative characters I'm more inclined to leave. Agreed?
On 12/16/2015 8:07 PM, Terry Reedy wrote:
On 12/16/2015 1:22 PM, George Trojan wrote:
I installed Python 3.1 on RHEL 7.2.
According to the output below, you installed 3.5.1. Much better than
the years old 3.1.
This was not my only mistake. I ran the test on Fedora 19, not RHEL 7.2.
The c
Hey guys,
I wrote a python package to deal with heatmiser's protocol when communicating
with devices over TCP.
It would be good to wrap some tests around it as I know the core elements won't
change - but need to add support for different devices and different connection
methods.
One thing has
On 18/12/2015 08:44, IBRAHIM ARANSIOLA RIDWAN via Python-list wrote:
Hi,
My name is ridwan and I have a problem with installing the version 3.5.1 on my
windows 10 system.
My question is those python have specified compatibility issues or I downloaded
the wrong version for my operating system,
Hi,
My name is ridwan and I have a problem with installing the version 3.5.1 on my
windows 10 system.
My question is those python have specified compatibility issues or I downloaded
the wrong version for my operating system, or do I need to change my system
settings in some aspect.
Thank you in
eryk sun at 2015/12/18 UTC+8 6:26:02PM wrote：
> The function's calling convention is x86 cdecl (CDLL, caller stack
> cleanup), but you're using the x86 stdcall convention (WinDLL, callee
> stack cleanup). For a 64-bit process they're actually the same, but
> you're using 32-bit Python, so you have
On Fri, Dec 18, 2015 at 3:51 AM, Steven D'Aprano wrote:
> On Fri, 18 Dec 2015 11:02 am, Mark Lawrence wrote:
>
>> A lot of it is down to Windows, as the actual complaint is:-
>>
>> six.print_(source)
>
> Looks like a bug in six to me.
>
> See, without Unicode comments in the std lib, you neve
On Fri, Dec 18, 2015 at 2:41 AM, wrote:
> ValueError: Procedure probably called with too many arguments (4 bytes in
> excess
The function's calling convention is x86 cdecl (CDLL, caller stack
cleanup), but you're using the x86 stdcall convention (WinDLL, callee
stack cleanup). For a 64-bit proc
On Fri, 18 Dec 2015 06:12 pm, Serhiy Storchaka wrote:
> Using non-ASCII apostrophes and like in docstrings may be considered a
> bug.
Absolutely not a bug. In Python 3, docstrings are Unicode, not bytes, and
can contain any valid (or even invalid) Unicode code points, including
non-characters.
On Fri, 18 Dec 2015 11:02 am, Mark Lawrence wrote:
> A lot of it is down to Windows, as the actual complaint is:-
>
> six.print_(source)
Looks like a bug in six to me.
See, without Unicode comments in the std lib, you never would have found
that bug.
--
Steven
--
https://mail.python.o
On Fri, 18 Dec 2015 05:51 pm, Chris Angelico wrote:
> I would be inclined to ASCIIfy the apostrophes, dashes, and the
> connection.py space that started this thread. People's names, URLs,
> and demonstrative characters I'm more inclined to leave. Agreed?
No.
--
Steven
--
https://mail.pytho
On Fri, 18 Dec 2015 10:05 am, Mark Lawrence asked:
"Should stdlib files contain 'narrow non breaking space' U+202F?"
Absolutely it should.
What better way to ensure that the interpreter works correctly with Unicode
than to use Unicode in the std lib?
--
Steven
--
https://mail.python.org/ma
On Fri, Dec 18, 2015 at 7:32 PM, Zachary Ware
wrote:
> On Fri, Dec 18, 2015 at 1:43 AM, Chris Angelico wrote:
>> On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka
>> wrote:
>>> Agreed. Please open an issue.
>>>
>>> Using non-ASCII apostrophes and like in docstrings may be considered a bug.
>>
>
Christian Gollwitzer wrote:
> Tk calls out into the native file manager to perform the file/open
> operation (on Win&Mac, on Unix it brings it's own).
This means, on Windows the user gets a "well known" file/directory browser?
Then this is an important feature!
Anything new and unknown is bad f
I am trying to use the libusb-win32 v1.2.6.0 with Win7. I wrote a test
program(showing below) but stuck with a strange problem. Here is the result:
D:\Work\Python34>python
Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:43:06) [MSC v.1600 32 bit (In
tel)] on win32
T
Am 16.12.15 um 14:18 schrieb Ulli Horlacher:
Is there an alternative to Tk's askopenfilename() and askdirectory()?
I want to select a files and directories within one widget, but
askopenfilename() let me only select files and askdirectory() let me only
select directories.
Tk calls out into th
On 18.12.15 09:43, Chris Angelico wrote:
On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka wrote:
Agreed. Please open an issue.
Using non-ASCII apostrophes and like in docstrings may be considered a bug.
http://bugs.python.org/issue25899
Thanks.
Also noticed this. Is this a markup error?
On Fri, Dec 18, 2015 at 1:43 AM, Chris Angelico wrote:
> On Fri, Dec 18, 2015 at 6:12 PM, Serhiy Storchaka wrote:
>> Agreed. Please open an issue.
>>
>> Using non-ASCII apostrophes and like in docstrings may be considered a bug.
>
> http://bugs.python.org/issue25899
>
> Also noticed this. Is this
23 matches
Mail list logo
