Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #109924 > unrolled thread

Python 3.6.0a2 is now available

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Python 3.6.0a2 is now available Ned Deily <nad@python.org> - 2016-06-13 23:57 -0400
    Re: Python 3.6.0a2 is now available cjw <cjwilliams43@gmail.com> - 2016-06-15 06:38 -0700
      Re: Python 3.6.0a2 is now available MRAB <python@mrabarnett.plus.com> - 2016-06-15 15:19 +0100
        Re: Python 3.6.0a2 is now available Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-15 21:36 -0700
          Re: Python 3.6.0a2 is now available Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-06-16 18:41 +1000

#109924 — Python 3.6.0a2 is now available

On behalf of the Python development community and the Python 3.6 release
team, I'm happy to announce the availability of Python 3.6.0a2.
3.6.0a2 is the first of four planned alpha releases of Python 3.6,
the next major release of Python.  During the alpha phase, Python 3.6
remains under heavy development: additional features will be added
and existing features may be modified or deleted.  Please keep in mind
that this is a preview release and its use is not recommended for
production environments.

You can find Python 3.6.0a2 here:

https://www.python.org/downloads/release/python-360a2/ 

The next release of Python 3.6 will be 3.6.0a3, currently scheduled for
2016-07-11.

Enjoy!

--Ned

--
  Ned Deily
  nad@python.org -- []

[toc] | [next] | [standalone]

#109967

On Monday, 13 June 2016 23:57:20 UTC-4, Ned Deily  wrote:
> On behalf of the Python development community and the Python 3.6 release
> team, I'm happy to announce the availability of Python 3.6.0a2.
> 3.6.0a2 is the first of four planned alpha releases of Python 3.6,
> the next major release of Python.  During the alpha phase, Python 3.6
> remains under heavy development: additional features will be added
> and existing features may be modified or deleted.  Please keep in mind
> that this is a preview release and its use is not recommended for
> production environments.
> 
> You can find Python 3.6.0a2 here:
> 
> https://www.python.org/downloads/release/python-360a2/ 
> 
> The next release of Python 3.6 will be 3.6.0a3, currently scheduled for
> 2016-07-11.
> 
> Enjoy!
> 
> --Ned
> 
> --
>   Ned Deily
>   nad@python.org -- []

I see that the Array Class now provides for data of the double type, this is good, but why is there no provision for data of the complex type?

Is this omission intended?

Colin W.

[toc] | [prev] | [next] | [standalone]

#109971

On 2016-06-15 14:38, cjw wrote:
> On Monday, 13 June 2016 23:57:20 UTC-4, Ned Deily  wrote:
>> On behalf of the Python development community and the Python 3.6 release
>> team, I'm happy to announce the availability of Python 3.6.0a2.
>> 3.6.0a2 is the first of four planned alpha releases of Python 3.6,
>> the next major release of Python.  During the alpha phase, Python 3.6
>> remains under heavy development: additional features will be added
>> and existing features may be modified or deleted.  Please keep in mind
>> that this is a preview release and its use is not recommended for
>> production environments.
>>
>> You can find Python 3.6.0a2 here:
>>
>> https://www.python.org/downloads/release/python-360a2/
>>
>> The next release of Python 3.6 will be 3.6.0a3, currently scheduled for
>> 2016-07-11.
>>
> I see that the Array Class now provides for data of the double type, this is good, but why is there no provision for data of the complex type?
>
> Is this omission intended?
>
The Array class supports types that are available in C, and, up until 
now, the source code of CPython has been based on the C89 standard, 
which lacks a complex type.

A complex type was added in the C99 standard.

Coincidentally, there was recently a discussion on the python-dev list 
about whether to switch to C99.

[toc] | [prev] | [next] | [standalone]

#110012

On Thursday, June 16, 2016 at 2:19:33 AM UTC+12, MRAB wrote:

> Coincidentally, there was recently a discussion on the python-dev list 
> about whether to switch to C99.

Only slightly less than a generation after it came out...

[toc] | [prev] | [next] | [standalone]

#110025

On Thursday 16 June 2016 14:36, Lawrence D’Oliveiro wrote:

> On Thursday, June 16, 2016 at 2:19:33 AM UTC+12, MRAB wrote:
> 
>> Coincidentally, there was recently a discussion on the python-dev list
>> about whether to switch to C99.
> 
> Only slightly less than a generation after it came out...

You say that as if this is the first time that anyone has raised this issue. It 
comes up, oh, at least once a year, sometimes more.

Like the last few dozen times, the answer is still no, we still can't switch to 
requiring C99 yet, as there are still users that rely on compilers with partial 
support for C99. But unlike previous times, now we can begin to use some C99 
features, provided they are available on the important C compilers we support. 

https://mail.python.org/pipermail/python-dev/2016-June/144876.html

You should read the whole thread before commenting:

https://mail.python.org/pipermail/python-dev/2016-June/144816.html



-- 
Steve

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web