Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Random832 Newsgroups: comp.lang.python Subject: Re: Well, I finally ran into a Python Unicode problem, sort of Date: Sun, 03 Jul 2016 22:16:27 -0400 Lines: 7 Message-ID: References: <0589521b-648a-47c1-8afa-6f746e0fb901@googlegroups.com> <1467598587.3816323.655944881.304DB95A@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Trace: news.uni-berlin.de etOFdK3mcYphc7E+7DXhMQqd+5diw298BgrVGHD7uMNw== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'operator': 0.03; 'subject:Python': 0.05; 'precedence': 0.09; 'received:internal': 0.09; 'subject:into': 0.09; 'message- id:@webmail.messagingengine.com': 0.16; 'operator.': 0.16; 'parser.': 0.16; 'received:10.202': 0.16; 'received:10.202.2': 0.16; 'received:10.202.2.212': 0.16; 'received:66.111': 0.16; 'received:66.111.4': 0.16; 'received:66.111.4.27': 0.16; 'received:io': 0.16; 'received:messagingengine.com': 0.16; 'received:out3-smtp.messagingengine.com': 0.16; 'received:psf.io': 0.16; 'subject:Unicode': 0.16; 'wrote:': 0.16; 'lawrence': 0.22; 'parser': 0.22; 'subject:problem': 0.22; 'header:In-Reply-To:1': 0.24; 'define': 0.27; 'could': 0.35; 'but': 0.36; 'to:addr:python- list': 0.36; 'subject:: ': 0.37; 'received:10': 0.37; 'received:66': 0.38; 'well.': 0.40; 'to:addr:python.org': 0.40; 'header:Message-Id:1': 0.61; 'remember,': 0.66; 'jul': 0.72 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=ze/GDbVVb7pdg/xqPyR9vXFYiJk=; b=BnpMes Ub5/ZRNAKiT18Srr0pF6+kcf36qEr3cDn9LrFo/yOje4vzvoFLktKGVi/tWbuvqh z5S2muiqJpkj5gGBXD6JF6NjuQpqo6y++43Fk2TLbQ+byAq3feHKSgxMLca5FpBD ZAMivigSH7BEFaePSkff5apo1LEn0Tm1j8zP0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=ze/GDbVVb7pdg/x qPyR9vXFYiJk=; b=aCgtS4mnnNBGd/pcbU10Q4RB+S6AEqDA13PyYwd9BxjxRhs 9ak74WrppjgGFY2pkebk+FuVuZK/bZVo3IwlN8NS7nD2Q22TvHZykSZni2dRhiCZ HoZ1tsVU9hSO8egZmaqUpzl0LXPykSb90Bg76C4RgDkZuu4dmOpXcFoNO0Cg= X-Sasl-Enc: Vybn3J8X+4PAKPBdm671z022iwmh8U/IKa/7PilAIjiJ 1467598587 X-Mailer: MessagingEngine.com Webmail Interface - ajax-15e5213e In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <1467598587.3816323.655944881.304DB95A@webmail.messagingengine.com> X-Mailman-Original-References: <0589521b-648a-47c1-8afa-6f746e0fb901@googlegroups.com> Xref: csiph.com comp.lang.python:111036 On Sun, Jul 3, 2016, at 20:00, Lawrence D=E2=80=99Oliveiro wrote: > That would be neat. But remember, you would have to define the operator > precedence as well. So you could no longer use a recursive-descent > parser. You could use a recursive-descent parser if you monkey-patch the parser when adding a new operator.