Re: [Python-Dev] Python 2.7 patch levels turning two digit

On 23.06.2014 18:09, Donald Stufft wrote: > > On Jun 23, 2014, at 2:09 AM, Martin v. Löwis wrote: > >>> >>> * Should we make use of the potential breakage with 2.7.10 >>> to introduce a new Windows compiler version for Python 2.7 ? >> >> Assuming it is a good idea to continue producing Windows

Re: [Python-Dev] Python 2.7 patch levels turning two digit

On 23.06.2014 22:20, Donald Stufft wrote: > > On Jun 23, 2014, at 3:27 PM, M.-A. Lemburg wrote: > >> On 23.06.2014 18:09, Donald Stufft wrote: >>> >>> On Jun 23, 2014, at 2:09 AM, Martin v. Löwis wrote: >>> >>>>> >>>>&

Re: [Python-Dev] surrogatepass - she's a witch, burn 'er! [was: Cleaning up ...]

On 29.08.2014 02:41, Stephen J. Turnbull wrote: > In the process of booking up for my other post in this thread, I > noticed the 'surrogatepass' handler. > > Is there a real use case for the 'surrogatepass' error handler? It > seems like a horrible break in the abstraction. IMHO, if there's a >

Re: [Python-Dev] surrogatepass - she's a witch, burn 'er! [was: Cleaning up ...]

On 29.08.2014 13:22, Isaac Morland wrote: > On Fri, 29 Aug 2014, M.-A. Lemburg wrote: > >> On 29.08.2014 02:41, Stephen J. Turnbull wrote: >> Since Python allows working with lone surrogates in Unicode (they >> are valid code points) and we're using UTF-8 for marsha

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 29.08.2014 21:47, Alex Gaynor wrote: > Hi all, > > I've just submitted PEP 476, on enabling certificate validation by default for > HTTPS clients in Python. Please have a look and let me know what you think. > > PEP text follows. Thanks for the PEP. I think this is generally a good idea, but

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 29.08.2014 23:11, Donald Stufft wrote: > > Sorry I was on my phone and didn’t get to fully reply to this. > >> On Aug 29, 2014, at 4:00 PM, M.-A. Lemburg wrote: >> >> On 29.08.2014 21:47, Alex Gaynor wrote: >>> Hi all, >>> >>> I've

Re: [Python-Dev] surrogatepass - she's a witch, burn 'er! [was: Cleaning up ...]

On 30.08.2014 01:37, Greg Ewing wrote: > M.-A. Lemburg wrote: >> we needed >> a way to make sure that Python 3 also optionally supports working >> with lone surrogates in such UTF-8 streams (nowadays called CESU-8: >> http://en.wikipedia.org/wiki/CESU-8). > >

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 30.08.2014 04:44, Alex Gaynor wrote: > Thanks for the rapid feedback everyone! > > I want to summarize the action items and discussion points that have come up > so > far: > > To add to the PEP: > > * Emit a warning in 3.4.next for cases that would raise a Exception in 3.5 > * Clearly state

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 30.08.2014 12:40, Antoine Pitrou wrote: > On Sat, 30 Aug 2014 12:19:11 +0200 > "M.-A. Lemburg" wrote: >>> To add to the PEP: >>> >>> * Emit a warning in 3.4.next for cases that would raise a Exception in 3.5 >>> * Clearly state tha

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 30.08.2014 12:55, Antoine Pitrou wrote: > On Sat, 30 Aug 2014 12:46:47 +0200 > "M.-A. Lemburg" wrote: >> The change is to the OpenSSL API, not the OpenSSL lib. By setting >> the variable you enable a few special calls to the config loader >> functions in OpenS

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 30.08.2014 15:32, R. David Murray wrote: > On Sat, 30 Aug 2014 14:03:57 +0200, "M.-A. Lemburg" wrote: >> On 30.08.2014 12:55, Antoine Pitrou wrote: >>> On Sat, 30 Aug 2014 12:46:47 +0200 >>> "M.-A. Lemburg" wrote: >>>>> That use

Re: [Python-Dev] PEP 476: Enabling certificate validation by default!

On 01.09.2014 10:09, Nick Coghlan wrote: > On 1 September 2014 17:13, Christian Heimes wrote: >> On 01.09.2014 08:44, Nick Coghlan wrote: >>> Yes, it would have exactly the same security failure modes as >>> sitecustomize, except it would only fire if the application >>> imported the ssl module. >

Re: [Python-Dev] 3.5 release schedule PEP

On 24.09.2014 03:48, Nick Coghlan wrote: > On 24 September 2014 03:05, Steve Dower wrote: >> Larry Hastings wrote: >>> >>> On 09/19/2014 03:31 PM, Barry Warsaw wrote: >>> I think we need a Python 3.5 Release Schedule PEP. >>> >>> Just checked it in as PEP 478. It should show up here in a few minu

Re: [Python-Dev] 3.5 release schedule PEP

Thanks for the insights, Steve. More below... On 24.09.2014 18:52, Steve Dower wrote: > M.-A. Lemburg wrote: >> >> I'd rather be conservative here and wait for another Python release before >> switching VC versions. There are a few important questions that need answers

Re: [Python-Dev] Status of C compilers for Python on Windows

On 10.10.2014 11:26, Larry Hastings wrote: > > On 10/10/2014 08:07 AM, Paul Moore wrote: >> On 10 October 2014 01:29, Victor Stinner wrote: >>> What about the Python stable ABI? Would it be broken if we use a >>> different compiler? >>> >>> What about third party Python extensions? >>> >>> What a

Re: [Python-Dev] XP buildbot problem cloning from hg.python.org

On 26.10.2014 00:14, Ned Deily wrote: > In article , > David Bolen wrote: > >> David Bolen writes: >> >>> which appears to die mid-stream while receiving the manifests. >>> >>> So I'm sort of hoping there might be some record server-side as to why >>> things are falling apart mid-way. >> >> Jus

Re: [Python-Dev] [Python-checkins] cpython (2.7): #22650: test suite: load Unicode test data files from www.pythontest.net

On 06.11.2014 15:39, Brett Cannon wrote: > What is pythontest.net? Is it something we control, and if so how do we add > things to it for tests? Did I miss an email on python-dev or > python-committers about this? pythontest.net is a domain owned by the PSF and run by Donald Stufft and Benjamin (I

[Python-Dev] hg.python.org cloning troubles after Sep 13 changes

Just FYI (and for the archives), to perhaps save someone a few minutes: I've been hitting a problem with hg pull and hg clone on a box recently and after staring at it for a while, finally found the cause. Here's what hg printed: HG-Python/cpython> hg pull -u -b 2.7 abort: no suitable response f

Re: [Python-Dev] Redirection of ar.pycon.org

Hi Facunda, you should either write to webmas...@pycon.org, the conference ML or me directly, since I'm managing these the pycon.org subdomains. > On Thu, Dec 18, 2014, at 10:59, Facundo Batista wrote: >> Hi! >> >> Don't remember where to ask for changing the redirection of that >> domain name. S

Re: [Python-Dev] Compile Python on Windows (OpenSSL)

On 13.01.2015 23:04, Victor Stinner wrote: > Hi, > > To compile Python on Windows, there are a few information in the > Developer Guide: > https://docs.python.org/devguide/setup.html#windows-compiling > > Python 3.5 now requires Visual Studio 2010 *SP1*, or newer Visual Studio: > http://bugs.pyth

Re: [Python-Dev] Compile Python on Windows (OpenSSL)

On 13.01.2015 23:42, Brian Curtin wrote: > On Tue, Jan 13, 2015 at 4:36 PM, Victor Stinner > wrote: >> 2015-01-13 23:18 GMT+01:00 Steve Dower : >>> Technically, Python 3.5 requires Visual Studio 2015 >> >> For me, it's *very* difficult to find how to install Visual Studio. >> There are many differ

Re: [Python-Dev] Compile Python on Windows (OpenSSL)

On 13.01.2015 23:50, Victor Stinner wrote: > 2015-01-13 23:46 GMT+01:00 M.-A. Lemburg : >> Just a note of caution: for older preview releases of VS the >> only way to get back to a clean system was to reinstall >> Windows. > > Does it mean that it's not poss

Re: [Python-Dev] Can Python Be Built Without Distutils

On 23.01.2015 19:48, Matthias Klose wrote: > On 01/23/2015 06:30 PM, Cyd Haselton wrote: >> Related to my earlier question regarding building Python on Android >> and an undefined reference to dlopen error...I have the following >> question: Is it possible to build and install Python without havin

Re: [Python-Dev] Can Python Be Built Without Distutils

On 23.01.2015 21:56, Cyd Haselton wrote: > On Fri, Jan 23, 2015 at 1:19 PM, M.-A. Lemburg wrote: >> On 23.01.2015 19:48, Matthias Klose wrote: >>> On 01/23/2015 06:30 PM, Cyd Haselton wrote: >>>> Related to my earlier question regarding building Python on Android &

Re: [Python-Dev] Can Python Be Built Without Distutils

On 24.01.2015 21:23, Zachary Ware wrote: > On Saturday, January 24, 2015, Brett Cannon wrote: > >> On Fri Jan 23 2015 at 5:45:28 PM Gregory P. Smith > > wrote: >> >>> On Fri Jan 23 2015 at 11:20:02 AM M.-A. Lemburg >> > wrote: >>> >>>

Re: [Python-Dev] Encoding of PyFrameObject members

On 06.02.2015 00:27, Francis Giraldeau wrote: > I need to access frame members from within a signal handler for tracing > purpose. My first attempt to access co_filename was like this (omitting > error checking): > > PyFrameObject *frame = PyEval_GetFrame(); > PyObject *ob = PyUnicode_AsUTF8Strin

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 03.04.2015 11:56, Larry Hastings wrote: > My Windows development days are firmly behind me. So I don't really have an > opinion here. So I put > it to you, Windows Python developers: do you care about GnuPG signatures on > Windows-specific files? > Or do you not care? Regardless of target

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 03.04.2015 19:35, Steve Dower wrote: >> My Windows development days are firmly behind me. So I don't really have an >> opinion here. So I put it to you, Windows Python developers: do you care >> about >> GnuPG signatures on Windows-specific files? Or do you not care? > > The later replies seem

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

heers, > Steve > > Top-posted from my Windows Phone > > From: M.-A. Lemburg<mailto:m...@egenix.com> > Sent: ‎4/‎3/‎2015 10:55 > To: Steve Dower<mailto:steve.do...@microsoft.com>; Larry > Hastings<mailto:la...@hastings.org>

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 04.04.2015 02:49, Donald Stufft wrote: > >> On Apr 3, 2015, at 6:38 PM, M.-A. Lemburg wrote: >> >> On 04.04.2015 00:14, Steve Dower wrote: >>> The thing is, that's exactly the same goodness as Authenticode gives, >>> except everyone gets that fo

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 04.04.2015 16:41, Steve Dower wrote: > "Relying only on Authenticode for Windows installers would result in a break > in technology w/r to the downloads we make available for Python, since all > other files are (usually) GPG signed" > > This is the point of this discussion. I'm willing to mak

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

to every signed file, just like an SSL cert is attached >> to a site or an S/MIME cert is embedded in a signed email. >> >> Cheers, >> Steve >> >> Top-posted from my Windows Phone >> ________ >> From: Steve Dower<mailto:st

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 04.04.2015 21:49, Kurt B. Kaiser wrote: > > > On Sat, Apr 4, 2015, at 03:35 PM, M.-A. Lemburg wrote: >> On 04.04.2015 21:02, Kurt B. Kaiser wrote: >>> For the record, that is a Symantec/Verisign code signing >>> certificate. We paid $1123 for it last

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 16.04.2015 21:34, "Martin v. Löwis" wrote: > Am 04.04.15 um 21:54 schrieb M.-A. Lemburg: >>>> FWIW: The PSF mostly uses StartSSL nowadays and they also support code >>>> signing certificates. Given that this option is a lot cheaper than >>>> Ver

Re: [Python-Dev] [python-committers] Do we need to sign Windows files with GnuPG?

On 17.04.2015 19:31, "Martin v. Löwis" wrote: > Am 17.04.15 um 00:46 schrieb M.-A. Lemburg: >>> I had asked the PSF for a StartSSL certificate when the previous >>> certificate expired, and the PSF was not able to provide one. After >>> waiting several week

Re: [Python-Dev] typeshed for 3rd party packages (was: Type hints -- a mediocre programmer's reaction)

On 21.04.2015 05:37, Guido van Rossum wrote: > On Mon, Apr 20, 2015 at 4:41 PM, Jack Diederich wrote: >> * Uploading stubs for other people's code is a terrible idea. Who do I >> contact when I update the interface to my library? The random Joe who >> "helped" by uploading annotations three months

Re: [Python-Dev] typeshed for 3rd party packages

On 21.04.2015 18:08, Guido van Rossum wrote: > On Tue, Apr 21, 2015 at 12:33 AM, M.-A. Lemburg wrote: > >> On 21.04.2015 05:37, Guido van Rossum wrote: >>> On Mon, Apr 20, 2015 at 4:41 PM, Jack Diederich >> wrote: >>>> * Uploading stubs for other peo

Re: [Python-Dev] Clarification of PEP 476 "opting out" section

On 30.04.2015 02:33, Nick Coghlan wrote: > Hi folks, > > This is just a note to highlight the fact that I tweaked the "Opting > out" section in PEP 476 based on various discussions I've had over the > past few months: https://hg.python.org/peps/rev/dfd96ee9d6a8 > > The notable changes: > > * the

Re: [Python-Dev] PYTHONHTTPSVERIFY env var (was: Clarification of PEP 476 "opting out" section)

On 07.05.2015 04:30, Nick Coghlan wrote: >> Can we please make the monkeypatch a regular part of Python's >> site.py which can enabled via an environment variable, say >> export PYTHONHTTPSVERIFY=0. >> >> See http://bugs.python.org/issue23857 for the discussion. > ... > I actually do think it would

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 08.05.2015 11:36, Nick Coghlan wrote: > On 8 May 2015 6:52 pm, "M.-A. Lemburg" wrote: >> >> On 07.05.2015 04:30, Nick Coghlan wrote: >>>> Can we please make the monkeypatch a regular part of Python's >>>> site.py which can enabled via an e

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 09.05.2015 02:29, Nick Coghlan wrote: > On 8 May 2015 8:14 pm, "M.-A. Lemburg" wrote: >> >> On 08.05.2015 11:36, Nick Coghlan wrote: >>> On 8 May 2015 6:52 pm, "M.-A. Lemburg" wrote: >>>> >>>> On 07.05.2015 04:30, Nick Coghla

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 10.05.2015 05:04, Robert Collins wrote: > On 10 May 2015 at 11:44, Chris Angelico wrote: >> On Sun, May 10, 2015 at 4:13 AM, M.-A. Lemburg wrote: >>> By providing a way to intentionally switch off the new default, >>> we do make people aware of the risks and th

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 11.05.2015 11:13, Nick Coghlan wrote: > On 11 May 2015 at 18:04, M.-A. Lemburg wrote: >> On 10.05.2015 05:04, Robert Collins wrote: >>> On 10 May 2015 at 11:44, Chris Angelico wrote: >>>> On Sun, May 10, 2015 at 4:13 AM, M.-A. Lemburg wrote: >>>>&g

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 11.05.2015 12:47, Nick Coghlan wrote: > On 11 May 2015 at 20:23, Donald Stufft wrote: >> On May 11, 2015, at 6:15 AM, Nick Coghlan wrote: >>> We made the decision when PEP 476 was accepted that this change turned >>> a silent security failure into a noisy one, rather than being a >>> regressio

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 11.05.2015 12:15, Nick Coghlan wrote: > On 11 May 2015 at 19:22, M.-A. Lemburg wrote: >> On 11.05.2015 11:13, Nick Coghlan wrote: >>> I wouldn't be opposed to seeing that as an upstream Python 2.7.x >>> feature, but agreement amongst redistributors on using

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 12.05.2015 05:03, Nick Coghlan wrote: > On 12 May 2015 at 04:49, M.-A. Lemburg wrote: >> On 11.05.2015 12:15, Nick Coghlan wrote: >>> By contrast, the configuration file shouldn't provide a new attack >>> vector (or simplify any existing attack vector), as

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 12.05.2015 12:04, Donald Stufft wrote: > >> On May 12, 2015, at 3:57 AM, M.-A. Lemburg wrote: >> >> In a user based installation (which most applications shipping >> their own Python installation are), you can always do this >> provided you can gain the appl

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 12.05.2015 13:19, Nick Coghlan wrote: > On 12 May 2015 at 21:17, Nick Coghlan wrote: >> Both of those make sense to me as cases where the environment variable >> based security downgrade approach is the "least bad" answer available, >> which is why I eventually agreed it should be one of the >>

Re: [Python-Dev] PYTHONHTTPSVERIFY env var

On 12.05.2015 13:21, Donald Stufft wrote: > >> On May 12, 2015, at 7:17 AM, Nick Coghlan wrote: >> >> On 12 May 2015 at 21:09, Donald Stufft wrote: >>> If you control the app you don't need to do that. All relevant api accept >>> the context parameter. The shims are only useful when you don't c

Re: [Python-Dev] Python initialization and embedded Python

On 18.11.2017 01:01, Victor Stinner wrote: > Hi, > > The CPython internals evolved during Python 3.7 cycle. I would like to > know if we broke the C API or not. > > Nick Coghlan and Eric Snow are working on cleaning up the Python > initialization with the "on going" PEP 432: > https://www.python.

Re: [Python-Dev] Python startup time

On 14.05.2018 18:26, Chris Barker via Python-Dev wrote: > > > On Fri, May 11, 2018 at 11:05 AM, Ryan Gonzalez > wrote: > > https://refi64.com/uprocd/ > > > very cool -- but *nix only, of course :-( > > But it seems that there is a demand for this sort of thing

Re: [Python-Dev] Microsoft to acquire GitHub for $7.5 billion

Something that may change is the way they treat Github accounts, after all, MS is very much a sales driven company. But then there's always the possibility to move to Gitlab as alternative (hosted or run on PSF VMs), so I would worry too much. Do note, however, that the value in Github is not so

Re: [Python-Dev] Computed Goto dispatch for Python 2

On 28.05.2015 02:17, Parasa, Srinivas Vamsi wrote: > Hi All, > > This is Vamsi from Server Scripting Languages Optimization team at Intel > Corporation. > > Would like to submit a request to enable the computed goto based dispatch in > Python 2.x (which happens to be enabled by default in Pytho

Re: [Python-Dev] Single-file Python executables (was: Computed Goto dispatch for Python 2)

You might want to have a look at eGenix PyRun, which gives you an almost complete Python runtime in 4-13MB (depending on what startup performance needs you have): http://www.egenix.com/products/python/PyRun/ On 28.05.2015 17:58, Barry Warsaw wrote: > On May 28, 2015, at 11:39 AM, Donald Stufft wr

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

On 01.06.2015 12:44, Armin Rigo wrote: > Hi Larry, > > On 31 May 2015 at 01:20, Larry Hastings wrote: >> p.s. Supporting this patch also helps cut into PyPy's reported performance >> lead--that is, if they ever upgrade speed.pypy.org from comparing against >> Python *2.7.2*. > > Right, we should

Re: [Python-Dev] 2.7 is here until 2020, please don't call it a waste.

and running for both Python 2 and 3 branches: https://speed.python.org/ What would it take to make that happen ? > Cheers, > fijal > > > On Mon, Jun 1, 2015 at 1:14 PM, M.-A. Lemburg wrote: >> On 01.06.2015 12:44, Armin Rigo wrote: >>> Hi Larry, >>&

Re: [Python-Dev] speed.python.org (was: 2.7 is here until 2020, please don't call it a waste.)

On 04.06.2015 04:08, Tetsuya Morimoto wrote: >> If someone were to volunteer to set up and run speed.python.org, I think > we could add some additional focus on performance regressions. Right now, > we don't have any way of reliably and reproducibly testing Python > performance. > > I'm very inter

Re: [Python-Dev] PEP 490: Chain exceptions at C level

On 20.06.2015 09:30, Victor Stinner wrote: > Hi, > > I didn't get much feedback on this PEP. Since the Python 3.6 branch is > open (default), it's probably better to push such change in the > beginning of the 3.6 cycle, to catch issues earlier. > > Are you ok to chain exceptions at C level by def

Re: [Python-Dev] speed.python.org

On 23.06.2015 03:58, Zachary Ware wrote: > On Thu, Jun 4, 2015 at 10:51 AM, Maciej Fijalkowski wrote: >> On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray >> wrote: >>> OK, so what you are saying is that speed.python.org will run a buildbot >>> slave so that when a change is committed to cPython,

Re: [Python-Dev] Backporting the 3.5+ Windows build project files to 2.7

On 22.06.2015 19:03, Zachary Ware wrote: > Hi, > > As you may know, Steve Dower put significant effort into rewriting the > project files used by the Windows build as part of moving to VC14 as > the official compiler for Python 3.5. Compared to the project files > for 3.4 (and older), the new pro

Re: [Python-Dev] Backporting the 3.5+ Windows build project files to 2.7

On 25.06.2015 17:12, Zachary Ware wrote: > On Thu, Jun 25, 2015 at 8:54 AM, M.-A. Lemburg wrote: >> On 22.06.2015 19:03, Zachary Ware wrote: >>> Using the backported project files to build 2.7 would require two >>> versions of Visual Studio to be installed; VS2010 (or n

Re: [Python-Dev] [python-committers] How are we merging forward from the Bitbucket 3.5 repo?

On 16.08.2015 16:08, Guido van Rossum wrote: > I presume the issue here is that Hg is so complicated that everyone knows a > different subset of the commands and semantics. > > I personally don't know what the commands for cherry-picking a revision > would be. > > I also don't know exactly what h

Re: [Python-Dev] PEP 0484 - the Numeric Tower

On 14.10.2015 01:37, Raymond Hettinger wrote: > >> On Oct 13, 2015, at 9:16 AM, Random832 wrote: >> >>> ## >>> ## Decimal has all of the methods specified by the Real abc, but it should >>> ## not be registered as a Real because decimals do not interoperate with >>> ## binary flo

Re: [Python-Dev] Translate Python language

On 11.11.2015 17:20, Donald Stufft wrote: > On November 11, 2015 at 11:19:07 AM, Paul Moore (p.f.mo...@gmail.com) wrote: >> On 11 November 2015 at 15:13, Christophe Bal wrote: >>> Hello. >>> >>> I'm a french teacher and I would like to use Python with young child but >>> I've a big problem. All the

Re: [Python-Dev] Support of UTF-16 and UTF-32 source encodings

On 14.11.2015 23:56, Victor Stinner wrote: > These encodings are rarely used. I don't think that any text editor use > them. Editors use ascii, latin1, utf8 and... all locale encoding. But I > don't know any OS using UTF-16 as a locale encoding. UTF-32 wastes disk > space. UTF-16 is used a lot for

Re: [Python-Dev] Reading Python source file

On 17.11.2015 02:53, Serhiy Storchaka wrote: > I'm working on rewriting Python tokenizer (in particular the part that reads > and decodes Python > source file). The code is complicated. For now there are such cases: > > * Reading from the string in memory. > * Interactive reading from the file. >

Re: [Python-Dev] Reading Python source file

On 17.11.2015 16:22, Guido van Rossum wrote: > On Tue, Nov 17, 2015 at 1:59 AM, M.-A. Lemburg wrote: >>> [moving from read source line by line to reading all in one go] >> We use the same simplification in eGenix PyRun's emulation of >> the Python command line in

Re: [Python-Dev] Python stdlib ssl.SSLContext is missing mode setting ability

On 19.11.2015 09:14, Cory Benfield wrote: > >> On 19 Nov 2015, at 03:53, Ben Bangert wrote: >> >> In Python 2 and 3, the ssl module's SSLContext object has a way to set >> SSL options, but not to set SSL modes. >> >> The set_mode command and some of the available modes: >> https://www.openssl.org

Re: [Python-Dev] Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

I think the PEP is a good step forward to compromise between the crypto purists (use whatever technologies makes us more secure even if it breaks things) and those who cannot upgrade their Python 2.7 because of the PEP 476 change, since it causes their applications to fail (e.g. because the embedde

Re: [Python-Dev] Deleting with setting C API functions

On 02.12.2015 13:29, Serhiy Storchaka wrote: > On 02.12.15 12:06, Victor Stinner wrote: >> 2015-12-02 9:42 GMT+01:00 Serhiy Storchaka : >>> You have enough time to update your projects, and you can update them >>> uniformly for all versions. And may be you will found few weird bugs related >>> to m

Re: [Python-Dev] Python Language Reference has no mention of list comprehensions

On 03.12.2015 14:37, Paul Moore wrote: > On 3 December 2015 at 12:51, Laura Creighton wrote: >> Intentional or Oversight? > > Hard to find :-) > > https://docs.python.org/3/reference/expressions.html#displays-for-lists-sets-and-dictionaries > > I went via "Atoms" in the expression section, then

Re: [Python-Dev] Python Language Reference has no mention of list comÃprehensions

On 03.12.2015 17:09, Ryan Gonzalez wrote: > > > On December 3, 2015 8:26:23 AM CST, Laura Creighton wrote: >> In a message of Thu, 03 Dec 2015 13:37:17 +, Paul Moore writes: >>> On 3 December 2015 at 12:51, Laura Creighton wrote: Intentional or Oversight? >>> >>> Hard to find :-) >>> >

Re: [Python-Dev] Python Language Reference has no mention of list comÃprehensions

On 03.12.2015 18:30, Laura Creighton wrote: > What I would like is if it were a lot easier for a person who just > saw a list comprehension for the very first time, and was told what it > is, to have a much, much easier time finding it in the Reference Manual. Such a person should more likely be d

Re: [Python-Dev] Python Language Reference has no mention of list comÃprehensions

On 03.12.2015 19:27, Laura Creighton wrote: > So how do we get search to work so that people in the Language > Reference who type in 'List Comprehension' get a hit? It seems that the search index is broken for at least a few documentation file releases: ok: https://docs.python.org/2.6/search.htm

Re: [Python-Dev] Do windows 10 users, like windows 7 users need to install a SP before installing Python will work?

On 07.12.2015 21:50, Laura Creighton wrote: > As webmaster, I am dealing with 3 unhappy would-be python users who have > windows 10. > > Right now their first problem is that when they click on the big > yellow button here: https://www.python.org/downloads/ > > instead of getting a download of 3.

Re: [Python-Dev] Branches in which to fix the SSL tests

On 07.01.2016 04:06, Martin Panter wrote: > Currently some SSL tests in the test suite are broken by a recent > certificate change at https://svn.python.org/; see > for the bug report. The tests are > broken when the test suite is run with the “-unetwork” option

Re: [Python-Dev] Update PEP 7 to require curly braces in C

On 18.01.2016 08:00, Victor Stinner wrote: > I like if without braces when the body is only one line, especially when > there is no else block. Same here. Compilers warn about these things today, so I don't think we need to go paranoid ;-) > Victor > > > Le dimanche 17 janvier 2016, Brett Cann

Re: [Python-Dev] Update PEP 7 to require curly braces in C

On 19.01.2016 00:20, Brett Cannon wrote: > On Sun, 17 Jan 2016 at 11:10 Brett Cannon wrote: > >> While doing a review of http://bugs.python.org/review/26129/ I asked to >> have curly braces put around all `if` statement bodies. Serhiy pointed out >> that PEP 7 says curly braces are optional: >> h

Re: [Python-Dev] More optimisation ideas

On 30.01.2016 20:15, Steve Dower wrote: > Brett tried freezing the entire stdlib at one point (as we do for parts of > importlib) and reported no significant improvement. Since that rules out code > compilation as well as the OS calls, it'd seem the priority is to execute > less code on startup.

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

On 03.02.2016 22:03, Victor Stinner wrote: > Hi, > > There is an old discussion about the performance of PyMem_Malloc() > memory allocator. CPython is stressing a lot memory allocators. Last > time I made statistics, it was for the PEP 454: > "For example, the Python test suites calls malloc() , r

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

On 04.02.2016 13:29, Victor Stinner wrote: > Hi, > > 2016-02-04 11:17 GMT+01:00 M.-A. Lemburg : >>> Do you see any drawback of using pymalloc for PyMem_Malloc()? >> >> Yes: You cannot free memory allocated using pymalloc with the >> standard C lib free(). &g

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

On 04.02.2016 14:25, Victor Stinner wrote: > Thanks for your feedback, you are asking good questions :-) > > 2016-02-04 13:54 GMT+01:00 M.-A. Lemburg : >>> There are 536 calls to the functions PyMem_Malloc(), PyMem_Realloc() >>> and PyMem_Free(). >>> >>

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

On 12.02.2016 12:18, Victor Stinner wrote: > ping? Sorry, your email must gotten lost in my inbox. > 2016-02-08 15:18 GMT+01:00 Victor Stinner : >> 2016-02-04 15:05 GMT+01:00 M.-A. Lemburg : >>> Sometimes, yes, but we also do allocations for e.g. >>> parsing values

Re: [Python-Dev] PEP 493: HTTPS verification migration tools for Python 2.7

On 24.02.2016 12:28, Cory Benfield wrote: > >> On 24 Feb 2016, at 10:32, Nick Coghlan wrote: >> >> Security Considerations >> --- >> >> Relative to the behaviour in Python 3.4.3+ and Python 2.7.9->2.7.11, this >> approach does introduce a new downgrade attack against the defau

Re: [Python-Dev] PEP 493: HTTPS verification migration tools for Python 2.7

On 24.02.2016 21:39, Cory Benfield wrote: > >> On 24 Feb 2016, at 12:19, M.-A. Lemburg wrote: >> >> On 24.02.2016 12:28, Cory Benfield wrote: >>> >>>> On 24 Feb 2016, at 10:32, Nick Coghlan wrote: >>>> >>>> Security Consideration

Re: [Python-Dev] Very old git mirror under github user "python-git"

On 28.02.2016 18:46, Georg Brandl wrote: > On 02/27/2016 11:45 PM, Matthias Bussonnier wrote: >> Hi all, >> >> >>> On Feb 27, 2016, at 14:21, Alexander Walters >> > wrote: >>> >>> Can we even ask github to pull it down and reasonably expect them to comply? >>> Thei

Re: [Python-Dev] What does a double coding cookie mean?

On 16.03.2016 01:28, Guido van Rossum wrote: > I agree that the spirit of the PEP is to stop at the first coding > cookie found. Would it be okay if I updated the PEP to clarify this? > I'll definitely also update the docs. +1 The only reason to read up to two lines was to address the use of the

Re: [Python-Dev] What does a double coding cookie mean?

On 17.03.2016 15:55, Guido van Rossum wrote: > On Thu, Mar 17, 2016 at 5:04 AM, Serhiy Storchaka wrote: >>> Should we recommend that everyone use tokenize.detect_encoding()? >> >> Likely. However the interface of tokenize.detect_encoding() is not very >> simple. > > I just found that out yesterda

Re: [Python-Dev] What does a double coding cookie mean?

ttached an example implementation with tests, which works in Python 2.7 and 3. > On Wed, Mar 16, 2016 at 5:05 PM, Guido van Rossum wrote: >> On Wed, Mar 16, 2016 at 12:59 AM, M.-A. Lemburg wrote: >>> The only reason to read up to two lines was to address the use of >>

Re: [Python-Dev] What does a double coding cookie mean?

On 17.03.2016 18:53, Serhiy Storchaka wrote: > On 17.03.16 19:23, M.-A. Lemburg wrote: >> On 17.03.2016 15:02, Serhiy Storchaka wrote: >>> On 17.03.16 15:14, M.-A. Lemburg wrote: >>>> On 17.03.2016 01:29, Guido van Rossum wrote: >>>>> Should we recomme

Re: [Python-Dev] What does a double coding cookie mean?

On 17.03.2016 15:02, Serhiy Storchaka wrote: > On 17.03.16 15:14, M.-A. Lemburg wrote: >> On 17.03.2016 01:29, Guido van Rossum wrote: >>> Should we recommend that everyone use tokenize.detect_encoding()? >> >> I'd prefer a separate utility for this somewhere

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 27.05.2016 06:54, Raymond Hettinger wrote: > >> On May 25, 2016, at 3:29 AM, Christian Heimes wrote: >> >> I have three hashing-related patches for Python 3.6 that are waiting for >> review. Altogether the three patches add ten new hash algorithms to the >> hashlib module: SHA3 (224, 256, 384,

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 27.05.2016 13:03, Donald Stufft wrote: > >> On May 27, 2016, at 6:54 AM, M.-A. Lemburg wrote: >> >> IMO, relying on OpenSSL is a better strategy than providing >> (and maintaining) our own compatibility versions. Until OpenSSL >> has them, people can u

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 27.05.2016 17:44, Chris Barker - NOAA Federal wrote: >>> , which aren't in any wide spread use yet and >> probably won't be for quite a few years ahead. > > Anything added to the stdlib now will be in py3.6+, yes? > > Which won't be in widespread use for quite a few years yet, either. > > S

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 27.05.2016 18:41, Chris Barker wrote: > On Fri, May 27, 2016 at 9:35 AM, M.-A. Lemburg wrote: > >>> So if ( and that's a big if) it's possible to anticipate what will be >>> in widespread use in a couple years, getting it in now would be a good >>> t

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 27.05.2016 22:58, Ryan Gonzalez wrote: > On May 27, 2016 3:04 PM, "Victor Stinner" wrote: >> >> Le vendredi 27 mai 2016, M.-A. Lemburg a écrit : >>> >>> The current patch is 1.2MB for SHA-3 - that's pretty heavy for just >>> a few ha

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 27.05.2016 23:46, Donald Stufft wrote: > >> On May 27, 2016, at 5:41 PM, M.-A. Lemburg wrote: >> >> If we add this now, there should at least be an exit strategy >> to remove the code again, when OpenSSL ships with the same >> code, IMO. > > I think

Re: [Python-Dev] New hash algorithms: SHA3, SHAKE, BLAKE2, truncated SHA512

On 28.05.2016 23:13, Christian Heimes wrote: > On 2016-05-27 14:41, M.-A. Lemburg wrote: >> On 27.05.2016 22:58, Ryan Gonzalez wrote: >>> On May 27, 2016 3:04 PM, "Victor Stinner" wrote: >>>> >>>> Le vendredi 27 mai 2016, M.-A. Lemburg a écri

Re: [Python-Dev] [Infrastructure] bugs.python.org not reachable in IPv6?

On 04.11.2013 16:10, Benjamin Peterson wrote: > 2013/11/4 M.-A. Lemburg : >> On 04.11.2013 11:01, Victor Stinner wrote: >>> Hi, >>> >>> bugs.python.org is still not responding on IPv6. Can someone please >>> remove the record from pyth

Re: [Python-Dev] [Infrastructure] bugs.python.org not reachable in IPv6?

On 04.11.2013 11:01, Victor Stinner wrote: > Hi, > > bugs.python.org is still not responding on IPv6. Can someone please > remove the record from python.org DNS, or fix the IPv6 > configuration? > > It's an issue on my PC because my PC has IPv6 address and so it cannot > reach bugs.python.or

  1   2   3   4   5   6   7   8   9   10   >