On behalf of the Python development community and the Python 3.6 release
team, I'm excited to announce the availability of Python 3.6.0rc1. 3.6.0rc1
is the release candiate for Python 3.6, the next major release of
Python.
Code for 3.6.0 is now frozen. Assuming no release critical problems are
fo
Michael Torrie :
> On 12/06/2016 03:29 PM, Marko Rauhamaa wrote:
>> Another thing is that, as stated before, the runlevel business is
>> legacy. It is still supported by systemd-update-utmp, but for how
>> long is anybody's guess.
>
> System V compatibility is still important to Linux, and as long
On Wednesday 07 December 2016 10:37, BartC wrote:
> On 06/12/2016 21:44, Gregory Ewing wrote:
>> BartC wrote:
>
>>> And the justification? Well, %ENVIRONMENTVARIABLE% gets converted in
>>> Windows, so why not?!
>>
>> No, the justification is that the Unix convention allows
>> the shell to provide
Tim Chase :
> On 2016-12-07 00:29, Marko Rauhamaa wrote:
>> A word a warning: your code doesn't lock /var/run/utmp before
>> access, which is a race condition. The file may be updated at any
>> time, and ordinary file reads may yield corrupted records.
>
> Since the code is reading in record-sized
On Wednesday 07 December 2016 12:55, BartC wrote:
> But even Linux's 128KB will fill if someone wanted a command line that
> listed 20,000 files individually. But it would be spectacularly bad use
> of a command line interface which was designed for humans.
That's EXACTLY the point of having the
On Tue, Dec 6, 2016 at 10:35 PM, Nathan Ernst wrote:
> One other consideration in regards to globbing in the argument list:
> there's a static limit to the byte length of argv. On windows, it's 8191
> bytes (I'm assuming a null-terminator brings that to 8192, which is a weird
> 2**13).
I know str
On 2016-12-06 21:27, Wildman via Python-list wrote:
> On Tue, 06 Dec 2016 13:06:35 -0600, Tim Chase wrote:
> I forgot to mention that I want to include your name in the
> final script as a contributor, if that is ok.
No issues here.
> You will get a cut of the royalties. Lets see, how much is
>
On Wed, Dec 7, 2016 at 1:30 AM, Dennis Lee Bieber wrote:
> (Bah... win10 seems to share parts of the PowerShell console config with
> the old command prompt -- making it nearly impossible [at least in the
> three days I've been on Win10 after the Win7 drive failed] to configure
> PowerShell to loo
On Tue, 06 Dec 2016 13:06:35 -0600, Tim Chase wrote:
>
I forgot to mention that I want to include your name in the
final script as a contributor, if that is ok.
You will get a cut of the royalties. Lets see, how much is
20% of $0.00? Well, I'll let my account work that out as
soon as she gets
On Tue, 06 Dec 2016 09:45:05 -0700, Michael Torrie wrote:
> I appreciate your measured response to what could be seen as an
> inflammatory post.
It was inflammatory and I considered a different response but
after the knee jerking, I give it some thought and decided
otherwise. The simple fact is
On 12/06/2016 03:21 AM, BartC wrote:
On 06/12/2016 07:37, Larry Hudson wrote:
Now you're suggesting the _shell_ is going to read and process a CVS
file???
What follows a shell command is a set of values a,b,c,d,e. What is encountered
in a CSV is a set
of values a,b,c,d,e. You really can't se
On 07Dec2016 01:55, BartC wrote:
On 06/12/2016 22:35, Nathan Ernst wrote:
One other consideration in regards to globbing in the argument list:
there's a static limit to the byte length of argv. On windows, it's 8191
bytes
That's the length of the command line, where parameters might still be
On 06Dec2016 23:37, BartC wrote:
(Actually at this point I haven't got a clue as to how Unix applications are
distributed. I guess it's not as simple as just providing a binary executable.
Given that UNIX systems run on many many different processors, this has limited
utility :-)
For the m
On Wed, 7 Dec 2016 12:25 am, BartC wrote:
> Or someone from Britain visiting the USA and saying OMG, everyone's got
> a gun! Suppose someone runs amok and shoots everybody!
Fun fact: there's a school shooting in the US about once a week.
http://www.huffingtonpost.com.au/entry/school-shootings-si
On Tue, Dec 6, 2016 at 3:05 PM, Random832 wrote:
>
> The fact that Windows was launched at boot by running "win.com" (either
> in autoexec.bat or manually at the command line) created a *perception*
> that windows ran "on top of DOS", but running it really *replaced* DOS
> in memory, putting the C
On Tue, 6 Dec 2016 06:08 pm, Gregory Ewing wrote:
>> And if there's an error in an option, you may have to abort, which means
>> throwing away that list of files which, in some cases, can run into
>> millions.
>
> This "millions of files" thing seems to be an imaginary
> monster you've invented t
On Tue, 6 Dec 2016 06:37 pm, Larry Hudson wrote:
> On 12/05/2016 10:50 AM, BartC wrote:
[...]
>> One would be very annoyed if, reading a CSV file, where each of N values
>> on a line correspond to a field of record, if one entry of "?LBC"
>> expanded itself to a dozen entries, screwing everything
On 06/12/2016 22:35, Nathan Ernst wrote:
One other consideration in regards to globbing in the argument list:
there's a static limit to the byte length of argv. On windows, it's 8191
bytes
That's the length of the command line, where parameters might still be
in the form *.*, ie. pre-splitting
On 2016-12-07 00:29, Marko Rauhamaa wrote:
> Tim Chase :
>
> > This works based on my poking at it in both Py2 and Py3:
>
> Great info, Tim.
>
> A word a warning: your code doesn't lock /var/run/utmp before
> access, which is a race condition. The file may be updated at any
> time, and ordinary
On Dec 6, 2016 4:04 PM, wrote:
On Tuesday, December 6, 2016 at 9:35:19 PM UTC, Ian wrote:
> On Mon, Dec 5, 2016 at 7:45 AM, clvanwall wrote:
> > I have been a Perl programmer for 15+ years and decided to give Python
a try. My platform is windows and I installed the latest 3.5.2. Next I
decided t
On 12/06/2016 04:37 PM, BartC wrote:
> How does that work?
>
> Suppose I provide an assortment of applications that would work better
> if wildcards are expanded.
>
> Do I then have to provide one more application, a shell, to be run first
> if someone wants to run any of my applications? Which
On 06/12/2016 21:44, Gregory Ewing wrote:
BartC wrote:
And the justification? Well, %ENVIRONMENTVARIABLE% gets converted in
Windows, so why not?!
No, the justification is that the Unix convention allows
the shell to provide certain useful functions that Unix
users value.
If you don't want t
On 12/06/2016 03:29 PM, Marko Rauhamaa wrote:
> Another thing is that, as stated before, the runlevel business is
> legacy. It is still supported by systemd-update-utmp, but for how long
> is anybody's guess.
System V compatibility is still important to Linux, and as long as it
is, something resem
On Tuesday, December 6, 2016 at 9:35:19 PM UTC, Ian wrote:
> On Mon, Dec 5, 2016 at 7:45 AM, clvanwall wrote:
> > I have been a Perl programmer for 15+ years and decided to give Python a
> > try. My platform is windows and I installed the latest 3.5.2. Next I
> > decided to convert a perl progra
On 12/06/2016 03:35 PM, Nathan Ernst wrote:
> One other consideration in regards to globbing in the argument list:
> there's a static limit to the byte length of argv. On windows, it's 8191
> bytes (I'm assuming a null-terminator brings that to 8192, which is a weird
> 2**13). For Linux, as of kern
On Wed, Dec 7, 2016 at 9:35 AM, Nathan Ernst wrote:
> One other consideration in regards to globbing in the argument list: there's
> a static limit to the byte length of argv. On windows, it's 8191 bytes (I'm
> assuming a null-terminator brings that to 8192, which is a weird 2**13). For
> Linux, a
One other consideration in regards to globbing in the argument list:
there's a static limit to the byte length of argv. On windows, it's 8191
bytes (I'm assuming a null-terminator brings that to 8192, which is a weird
2**13). For Linux, as of kernal 2.6.25, apparently, the limit is 131072
bytes, an
Tim Chase :
> This works based on my poking at it in both Py2 and Py3:
Great info, Tim.
A word a warning: your code doesn't lock /var/run/utmp before access,
which is a race condition. The file may be updated at any time, and
ordinary file reads may yield corrupted records.
The library function
On Wed, Dec 7, 2016 at 8:46 AM, Cameron Simpson wrote:
> Nothing prevents you writing an extremely simple shell yourself you know. It
> needn't expand anything. _Or_ you could have it adopt the inverse
> convention: expand nothing unless asked. Eg:
>
> cp G:*.c
>
> to cause "*.c" to get expanded.
On 06Dec2016 16:41, BartC wrote:
On 06/12/2016 15:44, Michael Torrie wrote:
On 12/06/2016 04:43 AM, BartC wrote:
Yes shell expansion has it's gotchas. But those can all be learned,
Yes, learn to avoid wildcards in command parameters at all costs. But
we both know that is not satisfactory.
BartC wrote:
But those would be silly.
Some special syntax is known about: | < and > for example. % less so
What you need to understand is that, to a Unix user,
* and ? are *just as well known* as |, < and >. Perhaps
even more so, because they're likely to be used much
sooner than piping and r
On Mon, Dec 5, 2016 at 7:45 AM, clvanwall wrote:
> I have been a Perl programmer for 15+ years and decided to give Python a try.
> My platform is windows and I installed the latest 3.5.2. Next I decided to
> convert a perl program that uses a ndbm database since according to the doc
> on pytho
BartC wrote:
What, the convention of NOT assuming that any command parameter that
uses * or ? MUST refer to whatever set of filenames happen to match in
the current directory?
Yes.
That's a pretty good convention, yes?!
That's a matter of opinion. It precludes the shell from
performing var
On Tue, 06 Dec 2016 13:06:35 -0600, Tim Chase wrote:
> On 2016-12-06 12:10, Wildman via Python-list wrote:
>> If I had tried this in the beginning, it would have
>> save you a lot of work.
>>
>> Since both versions of the code works, which one do
>> you recommend? Or does it matter?
>
> Heh, I'
On 2016-12-06 12:10, Wildman via Python-list wrote:
> If I had tried this in the beginning, it would have
> save you a lot of work.
>
> Since both versions of the code works, which one do
> you recommend? Or does it matter?
Heh, I'm not sure it matters much. The code I provided should be
expand
On Tue, Dec 6, 2016 at 6:21 AM, wrote:
> Hi,
>
> I'm facing strange Django broken pipe error (Python 2.7 on Ubuntu) that
> apparently is a not fixed Django bug. Does anybody now how to fix it? I've
> been searching a lot and didn't find any solution.
>
> This error happens very irregularly by Pos
On Mon, Dec 5, 2016 at 5:06 PM, clvanwall wrote:
> will thid do? John
>
Looks like you need to use dbm.ndbm.open() instead of just dbm.open().
See the docs here for more info:
https://docs.python.org/3/library/dbm.html#module-dbm.ndbm
--
https://mail.python.org/mailman/listinfo/python-list
On Mon, 05 Dec 2016 16:08:57 -0600, Tim Chase wrote:
> On 2016-12-05 14:58, Wildman via Python-list wrote:
>> I there a way to detect what the Linux runlevel is from
>> within a Python program? I would like to be able to do
>> it without the use of an external program such as 'who'
>> or 'runleve
On Tuesday December 6 2016 12:36, in comp.lang.python, "BartC"
wrote:
> On 06/12/2016 17:00, MRAB wrote:
>> On 2016-12-06 13:52, BartC wrote:
>
>>> Some special syntax is known about: | < and > for example. % less so
>>> (I've never, ever used it in live input AFAIK).
>>>
>> [snip]
>>
>> You've
On 06/12/2016 17:00, MRAB wrote:
On 2016-12-06 13:52, BartC wrote:
Some special syntax is known about: | < and > for example. % less so
(I've never, ever used it in live input AFAIK).
[snip]
You've never used ImageMagick?
If you want to shrink an image to half its size:
convert dragon
On 2016-12-06 13:52, BartC wrote:
On 06/12/2016 13:34, Chris Angelico wrote:
On Wed, Dec 7, 2016 at 12:25 AM, BartC wrote:
What, the convention of NOT assuming that any command parameter that uses *
or ? MUST refer to whatever set of filenames happen to match in the current
directory? And to t
On 2016-12-06 13:08, eryk sun wrote:
On Tue, Dec 6, 2016 at 12:26 PM, Chris Angelico wrote:
On Tue, Dec 6, 2016 at 10:56 PM, BartC wrote:
In that directory (which was on Windows but accessible via a virtual Linux),
typing any Linux command followed by * would have required all 3.4 million
dir
On 12/06/2016 09:18 AM, Wildman via Python-list wrote:
> It is sad that you consider learning something new to
> be worthless. I used the term "worthlessware" in an
> economical sense, meaning it has little or no commercial
> value. However, from a learning standpoint I consider
> it to be pricel
On 06/12/2016 15:44, Michael Torrie wrote:
On 12/06/2016 04:43 AM, BartC wrote:
Yes shell expansion has it's gotchas. But those can all be learned,
Yes, learn to avoid wildcards in command parameters at all costs. But we
both know that is not satisfactory.
And it's not much help when som
On 12/06/2016 06:51 AM, Tim Chase wrote:
> Based on the OP's description, this is a small part of a much larger
> program. And I would personally rather maintain a large Python
> code-base than a large Bash code-base.
Absolutely. Especially when you consider inxi is 12,000 lines of bash
code in
On 12/06/2016 06:52 AM, BartC wrote:
> But those would be silly.
But why?
> Some special syntax is known about: | < and > for example. % less so
> (I've never, ever used it in live input AFAIK).
Yup and why would you think the ? * special syntax is not known about or
should be known about? Ver
On Tue, 06 Dec 2016 01:14:35 +0100, Bernd Nawothnig wrote:
> On 2016-12-05, Wildman wrote:
>> And I am trying to write it without using external programs, where
>> possible.
>
> That is not the Unix way.
Yes, but it is my way.
>> I am a hobby programmer and I've been trying to learn python
>> f
On 12/06/2016 04:43 AM, BartC wrote:
>> Read the Python documentation for argparse
>
> I just tried it, but it was too complex for me to set it up so as to
> discover with it did with * arguments.
>
>> Again, start with argparse... Any command line argument that is left
>> after it has
On Tue, Dec 6, 2016, at 02:01, Larry Hudson via Python-list wrote:
> On 12/05/2016 06:51 PM, Nathan Ernst wrote:
> > IIRC, command.com was a relic of Win9x running on top of DOS and was a
> > 16-bit executable, so inherently crippled (and probably never support by
> > the NT kernel). Whereby cmd.ex
On Mon, Dec 5, 2016, at 21:21, Dennis Lee Bieber wrote:
> They are languages in their own right, with their own rules.
>
> The Windows command prompt being one of the weakest -- it doesn't
> support arithmetic and local variables, nor (to my knowledge) looping
> constructs. BAT files a
On Tuesday, 6 December 2016 13:25:40 UTC, BartC wrote:
> On 06/12/2016 12:40, Gregory Ewing wrote:
> > BartC wrote:
> >> I've given a dozen examples where the shell's auto-expansion can screw
> >> things up.
> >
> > Only because you're taking Windows conventions and trying
> > to apply them to Uni
Hi,
I'm facing strange Django broken pipe error (Python 2.7 on Ubuntu) that
apparently is a not fixed Django bug. Does anybody now how to fix it? I've been
searching a lot and didn't find any solution.
This error happens very irregularly by Post request in Django. Sometimes it
works sometimes
On 2016-12-06 01:14, Bernd Nawothnig wrote:
> > I am a hobby programmer and I've been trying to learn python
> > for a few months now. The program is 'worthlessware' but it
> > is a 'learning experience' for me.
>
> It looks for me like a worthless learning experience.
Eh, one person's "wort
On 06/12/2016 13:34, Chris Angelico wrote:
On Wed, Dec 7, 2016 at 12:25 AM, BartC wrote:
What, the convention of NOT assuming that any command parameter that uses *
or ? MUST refer to whatever set of filenames happen to match in the current
directory? And to then insert N arbitrary filenames in
On Wed, Dec 7, 2016 at 12:25 AM, BartC wrote:
> What, the convention of NOT assuming that any command parameter that uses *
> or ? MUST refer to whatever set of filenames happen to match in the current
> directory? And to then insert N arbitrary filenames in the parameter list.
>
> That's a pretty
On 06/12/2016 12:26, Chris Angelico wrote:
On Tue, Dec 6, 2016 at 10:56 PM, BartC wrote:
In that directory (which was on Windows but accessible via a virtual Linux),
typing any Linux command followed by * would have required all 3.4 million
directory entries to be accessed in order to build a 3
On 06/12/2016 12:40, Gregory Ewing wrote:
BartC wrote:
I've given a dozen examples where the shell's auto-expansion can screw
things up.
Only because you're taking Windows conventions and trying
to apply them to Unix.
What, the convention of NOT assuming that any command parameter that
uses
On 2016-12-06, Chris Angelico wrote:
> On Tue, Dec 6, 2016 at 10:56 PM, BartC wrote:
>> In that directory (which was on Windows but accessible via a virtual Linux),
>> typing any Linux command followed by * would have required all 3.4 million
>> directory entries to be accessed in order to build
On Tue, Dec 6, 2016 at 12:26 PM, Chris Angelico wrote:
> On Tue, Dec 6, 2016 at 10:56 PM, BartC wrote:
>> In that directory (which was on Windows but accessible via a virtual Linux),
>> typing any Linux command followed by * would have required all 3.4 million
>> directory entries to be accessed
BartC wrote:
I've given a dozen examples where the shell's
auto-expansion can screw things up.
Only because you're taking Windows conventions and trying
to apply them to Unix.
That's like somebody from the USA visiting Britain and
thinking "OMG! These people are all going to get themselves
kil
On Tue, Dec 6, 2016 at 2:51 AM, Nathan Ernst wrote:
> On Mon, Dec 5, 2016 at 8:44 PM, Steve D'Aprano
> wrote:
>> On Tue, 6 Dec 2016 10:09 am, eryk sun wrote:
>>
>> > The default Windows shell is "cmd.exe", and it's informally called the
>> > "Command Prompt",
>>
>> Thanks for the correction, I al
On Tue, Dec 6, 2016 at 10:56 PM, BartC wrote:
> In that directory (which was on Windows but accessible via a virtual Linux),
> typing any Linux command followed by * would have required all 3.4 million
> directory entries to be accessed in order to build a 3.4 million-element
> argv list. I've no
On 2016-12-05 23:00, Wildman via Python-list wrote:
> On Mon, 05 Dec 2016 21:42:52 -0600, Tim Chase wrote:
> > This works based on my poking at it in both Py2 and Py3:
>
> That works perfectly. I owe you a big thanks. That was a
> lot of work and time on your part. I really appreciate it.
It w
On 06/12/2016 07:08, Gregory Ewing wrote:
BartC wrote:
And if there's an error in an option, you may have to abort, which
means throwing away that list of files which, in some cases, can run
into millions.
This "millions of files" thing seems to be an imaginary
monster you've invented to try
On 06/12/2016 02:21, Dennis Lee Bieber wrote:
On Mon, 5 Dec 2016 18:50:30 +, BartC declaimed the
following:
It doesn't matter, and is not the concern of the shell. It should
restrict itself to the basic parsing that may be necessary when
Another name for "shell" is "command line
On Tue, Dec 6, 2016 at 10:21 PM, BartC wrote:
> What follows a shell command is a set of values a,b,c,d,e. What is
> encountered in a CSV is a set of values a,b,c,d,e. You really can't see the
> similarity?
>
> Suppose instead of:
>
> command a b c d e
>
> The interface was changed to be more in
On 06/12/2016 07:37, Larry Hudson wrote:
Now you're suggesting the _shell_ is going to read and process a CVS
file???
What follows a shell command is a set of values a,b,c,d,e. What is
encountered in a CSV is a set of values a,b,c,d,e. You really can't see
the similarity?
Suppose instead o
On Monday, 5 December 2016 17:14:27 UTC, Skip Montanaro wrote:
> ISTR that the way DOS/Windows operate at the text prompt level was
> modeled on VMS. As you indicated, each command was responsible for its
> own "globbing". I've never programmed in DOS or Windows, and its been
> decades since I pro
On Monday, 5 December 2016 18:21:57 UTC, Chris Angelico wrote:
> On Tue, Dec 6, 2016 at 5:02 AM, BartC wrote:
> >
> > how do you tell whether the last file in an argument list is the optional
> > 'file', or the last file of the expansion of 'filespec'?
>
> Why should you care? I have used shell
69 matches
Mail list logo
