Terry Reedy wrote:
> On 2/22/2019 7:55 AM, songbird wrote:
>> eryk sun wrote:
>> ...
>>> The win-amd64 ABI is significantly different, but at the API level
>>> there isn't a drastic difference between 32-bit and 64-bit Windows, so
>>> there's no cognitive burden with perpetuating the Win32 name.
Terry Reedy wrote:
> On 2/22/2019 7:55 AM, songbird wrote:
>> eryk sun wrote:
>> ...
>>> The win-amd64 ABI is significantly different, but at the API level
>>> there isn't a drastic difference between 32-bit and 64-bit Windows, so
>>> there's no cognitive burden with perpetuating the Win32 name.
On 2/22/2019 7:55 AM, songbird wrote:
eryk sun wrote:
...
The win-amd64 ABI is significantly different, but at the API level
there isn't a drastic difference between 32-bit and 64-bit Windows, so
there's no cognitive burden with perpetuating the Win32 name. The
official API name was actually
Chris Angelico wrote:
>songbird wrote:
...
>> "Do I have temporary directory and file creation
>> permissions on this system or not?"
>
> Then ask that question instead! And the answer might well be here:
>
> https://docs.python.org/3/library/tempfile.html
if you recall my original post/code
eryk sun wrote:
...
> The win-amd64 ABI is significantly different, but at the API level
> there isn't a drastic difference between 32-bit and 64-bit Windows, so
> there's no cognitive burden with perpetuating the Win32 name. The
> official API name was actually changed to "Windows API" or WINAPI
Chris Angelico wrote:
> On Thu, Feb 21, 2019 at 12:56 AM songbird wrote:
>> Thomas Jollans wrote:
>> ...
>> > I'm fairly sure "win32" was used on W9x as well. In any case it *was*
>> > correct at the time, as early versions of Python also ran on DOS and
>> > Windows 3.1. "windows" would not have
Thomas Jollans schreef op 20/02/2019 om 12:48:
I'm fairly sure "win32" was used on W9x as well.
Indeed, it was used for all 32-bit Windows versions: both the 9x line
and the NT line. There were differences, of course. For example there
are many calls that take SECURITY_ATTRIBUTES
On Thu, Feb 21, 2019 at 12:56 AM songbird wrote:
>
> Thomas Jollans wrote:
> ...
> > I'm fairly sure "win32" was used on W9x as well. In any case it *was*
> > correct at the time, as early versions of Python also ran on DOS and
> > Windows 3.1. "windows" would not have been suitable.
> >
> > But
On Thu, Feb 21, 2019 at 1:00 AM songbird wrote:
> anyways, one thing i do like about an actual
> probe of the temporary kind is that i can answer
> the question of:
>
> "Do I have temporary directory and file creation
> permissions on this system or not?"
Then ask that question instead! And
Chris Angelico wrote:
> songbird wrote:
...
>> no win64?
>
> The value "win32" means Windows (or, more technically, "Windows NT
> family", as opposed to Win95/Win98 - but since Win XP, that's the only
> type of Windows there is). If you actually care about whether it's a
> 32-bit or 64-bit OS,
Thomas Jollans wrote:
...
> I'm fairly sure "win32" was used on W9x as well. In any case it *was*
> correct at the time, as early versions of Python also ran on DOS and
> Windows 3.1. "windows" would not have been suitable.
>
> But yeah, we're stuck with it. There are obviously good reasons that
On 2/20/19, Thomas Jollans wrote:
>
> I'm fairly sure "win32" was used on W9x as well. In any case it *was*
> correct at the time, as early versions of Python also ran on DOS and
> Windows 3.1. "windows" would not have been suitable.
DOS Python would be a separate platform. But if there was
On 20/02/2019 08.13, eryk sun wrote:
> On 2/19/19, Chris Angelico wrote:
>>
>> The value "win32" means Windows (or, more technically, "Windows NT
>> family", as opposed to Win95/Win98 - but since Win XP, that's the only
>> type of Windows there is). If you actually care about whether it's a
>>
On 2/19/19, Chris Angelico wrote:
>
> The value "win32" means Windows (or, more technically, "Windows NT
> family", as opposed to Win95/Win98 - but since Win XP, that's the only
> type of Windows there is). If you actually care about whether it's a
> 32-bit or 64-bit OS, you can look at
On Wed, Feb 20, 2019 at 6:29 AM Terry Reedy wrote:
>
> On 2/19/2019 10:06 AM, Chris Angelico wrote:
> > On Wed, Feb 20, 2019 at 2:04 AM Chris Angelico wrote:
> >>
> >> On Wed, Feb 20, 2019 at 1:59 AM songbird wrote:
> >>>
> >>> MRAB wrote:
> >>> ...
> Don't use a bare except, it'll catch
On 2/19/2019 10:06 AM, Chris Angelico wrote:
On Wed, Feb 20, 2019 at 2:04 AM Chris Angelico wrote:
On Wed, Feb 20, 2019 at 1:59 AM songbird wrote:
MRAB wrote:
...
Don't use a bare except, it'll catch _any_ exception.
that's ok with this code IMO, but i see your point.
Not really,
On Wed, Feb 20, 2019 at 3:26 AM Grant Edwards wrote:
>
> On 2019-02-19, Chris Angelico wrote:
>
> > Oh, and not just bugs either. If the user hits Ctrl-C at just the
> > right moment, KeyboardInterrupt will be raised. You'll swallow that
> > exception silently, preventing the user-requested
On 2019-02-19, Chris Angelico wrote:
> Oh, and not just bugs either. If the user hits Ctrl-C at just the
> right moment, KeyboardInterrupt will be raised. You'll swallow that
> exception silently, preventing the user-requested halt, and going and
> doing the wrong thing. Don't use a bare except
On 19/02/2019 14:35, songbird wrote:
Dan Sommers wrote:
...
Python 3.7.2 (default, Jan 10 2019, 23:51:51)
[GCC 8.2.1 20181127] on linux
Type "help", "copyright", "credits" or "license" for more information.
import sys
sys.platform
'linux'
this doesn't help me for the rest of the
On Wed, Feb 20, 2019 at 1:59 AM songbird wrote:
>
> MRAB wrote:
> ...
> > Don't use a bare except, it'll catch _any_ exception.
>
> that's ok with this code IMO, but i see your point.
>
Not really, no. It means that ANY bug (barring an outright syntax
error) inside the try block will silently
On Wed, Feb 20, 2019 at 2:04 AM Chris Angelico wrote:
>
> On Wed, Feb 20, 2019 at 1:59 AM songbird wrote:
> >
> > MRAB wrote:
> > ...
> > > Don't use a bare except, it'll catch _any_ exception.
> >
> > that's ok with this code IMO, but i see your point.
> >
>
> Not really, no. It means that
On Wed, Feb 20, 2019 at 1:51 AM songbird wrote:
> For other systems, the values are:
> System platform value
> Linux 'linux'
> Windows 'win32'
> Windows/Cygwin 'cygwin'
> Mac OS X'darwin'
>
> =
>
> no win64?
The value "win32" means Windows (or, more technically,
MRAB wrote:
...
> Don't use a bare except, it'll catch _any_ exception.
that's ok with this code IMO, but i see your point.
> If the regex matches, re.search will return a match object; if it
> doesn't match, it'll return None.
>
> In any case, +1 to Dan's answer.
>
> [snip]
ok, thanks!
Rick Johnson wrote:
...
> The standard idiom for regexp match objects is to test for truthiness, not to
> use an except-clause.
>
> m = re.search("^[A-Za-z]:", sysprobetmp)
> if m:
> ...
ok, thanks! :)
songbird
--
https://mail.python.org/mailman/listinfo/python-list
Dan Sommers wrote:
...
> Python 3.7.2 (default, Jan 10 2019, 23:51:51)
> [GCC 8.2.1 20181127] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import sys
> >>> sys.platform
> 'linux'
this doesn't help me for the rest of the platforms
available.
=
On 2019-02-18 02:46, songbird wrote:
having worked on some other things for a while i
didn't put much emphasis on working on this until i
had the other bugs taken care of.
so now back into it we can go... :)
what i came up with (sorry, i hate yet another not
invented here thing, but
On 2/17/19 8:46 PM, songbird wrote:
simply put. if i'm running on a computer and i
don't easily know why kind of computer how can i
answer this in a quick way without getting overly
complicated that also will cover most of the easy
cases?
i came up with this:
comments? additions?
songbird wrote:
...
> result = re.search("^/(tmp)|(var)|(usr)|(opt)|(home)", sysprobetmp)
i changed that line to:
result = re.search("^/((tmp)|(var)|(usr)|(opt)|(home))", sysprobetmp)
just to make sure the leading slash is not just grouped
with the first string. i like to be more
having worked on some other things for a while i
didn't put much emphasis on working on this until i
had the other bugs taken care of.
so now back into it we can go... :)
what i came up with (sorry, i hate yet another not
invented here thing, but this is just where i ended up
after
29 matches
Mail list logo
