Hi Sesha:
memoryview is part of the language. Even if you could hide or remove the
feature, you would be running a specially broken version of Python,
which can't be good. There is surely a better way to fix the code. If it
helps any, you're landing here:
https://hg.python.org/cpython/file/v
On 12/13/2016 8:47 AM, KH Luke Kim wrote:
Yeah, but is it supposed to be avoided to apply new features in Python
3.x to Python 2.x? Sorry if there's already a consensus.
The feature set of every Pythonx.y version is frozen with the release of
CPython x.y.0. Thereafter, each x.y.1+ release onl
Hi Ned,
please add a reminder to the release docs that Python 3.6.0 is not
compatible with OpenSSL 1.1.0c, https://bugs.python.org/issue28689.
1.1.0 to 1.1.0b work fine. 1.1.0d will be compatible, too.
Regards,
Christian
signature.asc
Description: OpenPGP digital signature
On 14 December 2016 at 05:10, Sesha Narayanan Subbiah
wrote:
> From http://legacy.python.org/download/, I could see that the current
> production releases are Python 3.4 and Python 2.7.6.
That URL seems to be out of date. You should refer to www.python.org,
specifically https://www.python.org/dow
On 13 December 2016 at 13:47, KH Luke Kim wrote:
> Yeah, but is it supposed to be avoided to apply new features in Python 3.x
> to Python 2.x? Sorry if there's already a consensus.
Yes. Only security-related new features will ever be backported to
Python 2 (and even those will be subject to discu
Thanks Rob. I will try upgrade to 2.7.12. Any idea of this memory view
object that has been back ported to 2.7 can be disabled in any way?
Thanks
Regards
Sesha
On Wed, Dec 14, 2016, 17:33 Robert Collins
wrote:
> On 14 December 2016 at 18:10, Sesha Narayanan Subbiah
> wrote:
> > Hi Rob
> >
> >
Hi Rob
Thanks for your reply.
>From http://legacy.python.org/download/, I could see that the current
production releases are Python 3.4 and Python 2.7.6.
Since we use python for some our legacy applications, we don't want to
switch to Python 3.0 right now. Moreover, since Python 2.6 is not suppo
> Is it possible to add a key, triggering a resize of the dict, then
remove one, and continue iterating through the old (deallocated)
memory?
You can add and remove keys between calling next which would resize the
dictionary; however, it will not iterate through uninitialized memory. The
dictiter
That helped a lot, thanks!
On Wed, 14 Dec 2016 at 4:58 AM Martin Panter wrote:
> On 13 December 2016 at 13:37, MRAB wrote:
>
> > On 2016-12-13 11:31, KH Luke Kim wrote:
>
> >>
>
> >> Hello,
>
> >> recently there had been some issues in audioread and librosa that 3-byte
>
> >> samples can be loa
> On 13 Dec 2016, at 17:52, Eric V. Smith wrote:
>
>
>> On Dec 13, 2016, at 11:42 AM, Raymond Hettinger
>> wrote:
>>
>>
>>> On Dec 13, 2016, at 1:51 AM, Max Moroz wrote:
>>>
>>> Would it be worth ensuring that an exception is ALWAYS raised if a key
>>> is added to or deleted from a dictio
Yeah, but is it supposed to be avoided to apply new features in Python 3.x
to Python 2.x? Sorry if there's already a consensus.
2016-12-13 22:37 GMT+09:00 MRAB :
> On 2016-12-13 11:31, KH Luke Kim wrote:
>
>> Hello,
>> recently there had been some issues in audioread and librosa that 3-byte
>> sa
On 14 December 2016 at 18:10, Sesha Narayanan Subbiah
wrote:
> Hi Rob
>
> Thanks for your reply.
>
> From http://legacy.python.org/download/, I could see that the current
> production releases are Python 3.4 and Python 2.7.6.
Nope - https://www.python.org/downloads/ - 2.7.12 and 3.5.2 are
current
12 matches
Mail list logo
