On Tue, Mar 29, 2022, 10:55 AM Brett Cannon wrote:
>
>
> On Tue, Mar 29, 2022 at 8:58 AM Ronald Oussoren
> wrote:
>
>>
>>
>> On 29 Mar 2022, at 00:34, Brett Cannon wrote:
>>
>>
>>
>> On Mon, Mar 28, 2022 at 11:52 AM Christopher Barker
>> wrote:
>>
>>> On Mon, Mar 28, 2022 at 11:29 AM Paul Moor
On Sun, Mar 27, 2022, 11:07 AM Paul Moore wrote:
> On Sun, 27 Mar 2022 at 17:11, Christopher Barker
> wrote:
> > Back to the topic at hand, rather than remove urllib, maybe it could be
> made better -- an as-easy-to-use-as-requests package in the stdlib would be
> really great.
>
> I think that'
This is an excellent enumeration of some of the concerns!
One minor comment about the introductory material:
On Mon, Nov 1, 2021 at 5:21 AM Petr Viktorin wrote:
> >
> > Introduction
> >
> >
> > Python code is written in `Unicode`_ – a system for encoding and
> > handling all kinds
On Fri, Oct 9, 2020, 5:30 AM Christian Heimes wrote:
> On 09/10/2020 04.04, Ivan Pozdeev via Python-Dev wrote:
> > I don't see the point of requiring to "write an apology", especially
> > *before a 12-month ban*. If they understand that their behavior is
> > wrong, there's no need for a ban, at l
On Mon, Aug 5, 2019 at 6:47 PM wrote:
>
> I wish people with more product management experience would chime in;
> otherwise, 3.8 is going to ship with an intentional hard-to-ignore annoyance
> on the premise that we don't like the way people have been programming and
> that they need to change
On Tue, Feb 26, 2019 at 2:07 PM Neil Schemenauer
wrote:
> On 2019-02-26, Gregory P. Smith wrote:
> > On Tue, Feb 26, 2019 at 9:55 AM Barry Warsaw wrote:
> > For an OS distro provided interpreter, being able to restrict its use to
> > only OS distro provided software would be ideal (so ideal that
On Thu, Nov 29, 2018, 6:56 AM Benjamin Peterson
>
> On Wed, Nov 28, 2018, at 15:27, Steven D'Aprano wrote:
> > On Wed, Nov 28, 2018 at 10:43:04AM -0800, Gregory P. Smith wrote:
> >
> > > PyPI makes getting more algorithms easy.
> >
> > Can we please stop over-generalising like this? PyPI makes get
On Sat, May 5, 2018, 10:40 AM Eric Fahlgren wrote:
> On Sat, May 5, 2018 at 10:30 AM, Toshio Kuratomi
> wrote:
>
>> On Fri, May 4, 2018, 7:00 PM Nathaniel Smith wrote:
>>
>>> What are the obstacles to including "preloaded" objects in regular .pyc
>&g
On Fri, May 4, 2018, 7:00 PM Nathaniel Smith wrote:
> What are the obstacles to including "preloaded" objects in regular .pyc
> files, so that everyone can take advantage of this without rebuilding the
> interpreter?
>
Would this make .pyc files arch specific?
-Toshio
__
On Jan 13, 2018 9:08 AM, "Christian Heimes" wrote:
Hi,
PEP 370 [1] was my first PEP that got accepted. I created it exactly one
decade and two days ago for Python 2.6 and 3.0.
I didn't know I had you to thank for this! Thanks Christian! This is one
of the best features of the python software
On Dec 9, 2017 8:53 PM, "INADA Naoki" wrote:
> Earlier versions of PEP 538 thus included "en_US.UTF-8" on the
> candidate target locale list, but that turned out to cause assorted
> problems due to the "C -> en_US" part of the coercion.
Hm, but PEP 538 says:
> this PEP instead proposes to exten
On Nov 7, 2017 5:47 AM, "Paul Moore" wrote:
On 7 November 2017 at 13:35, Philipp A. wrote:
> Sorry, I still don’t understand how any of this is a problem.
>
> If you’re an application developer, google “python disable
> DeprecationWarning” and paste the code you found, so your users don’t see
>
On Sat, Mar 4, 2017 at 11:50 PM, Nick Coghlan wrote:
>
> Providing implicit locale coercion only when running standalone
> ---
>
> Over the course of Python 3.x development, multiple attempts have been made
> to improve the handling of in
On Jun 14, 2016 8:32 AM, "Joao S. O. Bueno" wrote:
>
> On 14 June 2016 at 12:19, Steven D'Aprano wrote:
> > Is there
> > a good reason for returning bytes?
>
> What about: it returns 0-255 numeric values for each position in a
stream, with
> no clue whatsoever to how those values map to text cha
On Nov 26, 2015 4:53 PM, "Nick Coghlan" wrote:
>
> On 27 November 2015 at 03:15, Barry Warsaw wrote:
>
> > Likewise in Ubuntu, we try to keep deviations from Debian at a minimum,
and
> > document them when we must deviate. Ubuntu is a community driven
distro so
> > while Canonical itself has cu
On Tue, Nov 24, 2015 at 10:56 AM, Paul Moore wrote:
> On 24 November 2015 at 18:37, Toshio Kuratomi wrote:
>> The cornercases come
>> into play because you don't always control all of the devices and
>> services on your network. The site could evaluate and decide that
On Tue, Nov 24, 2015 at 10:08 AM, Paul Moore wrote:
> I'm not actually sure that it's the place of this PEP to even comment
> on what the long term answer for such environments should be (or
> indeed, any answer, long term or not). I've argued the position that
> in some organisations it feels li
On Mon, Nov 23, 2015 at 5:59 PM, Barry Warsaw wrote:
> I'm concerned about accepting PEP 493 making a strong recommendation to
> downstreams. Yes, in an ideal world we all want security by default, but I
> think the backward compatibility concerns of the PEP are understated,
> especially as they
On Nov 24, 2015 6:28 AM, "Laura Creighton" wrote:
>
> In a message of Tue, 24 Nov 2015 14:05:53 +, Paul Moore writes:
> >Simply adding "people who have no control over their broken
> >infrastructure" with a note that this PEP helps them, would be
> >sufficient here (and actually helps the case
On May 30, 2015 1:56 AM, "Nick Coghlan" wrote:
>
> Being ready, willing and able to handle the kind of situation created
> by the Python 2->3 community transition is a large part of what it
> means to offer commercial support for community driven open source
> projects, as it buys customers' time
On Tue, Apr 21, 2015 at 01:54:55PM -0400, Donald Stufft wrote:
>
> Anyways, I'll have access to the data set for another day or two before I
> shut down the (expensive) server that I have to use to crunch the numbers so
> if
> there's anything anyone else wants to see before I shut it down, speak
On Mon, Mar 23, 2015 at 04:14:52PM +0100, Antoine Pitrou wrote:
> On Mon, 23 Mar 2015 08:06:13 -0700
> Toshio Kuratomi wrote:
> > >
> > > I really think Donald has a good point when he suggests a specific
> > > virtualenv for system programs using Python.
>
On Mon, Mar 23, 2015 at 03:30:23PM +0100, Antoine Pitrou wrote:
> On Mon, 23 Mar 2015 07:22:56 -0700
> Toshio Kuratomi wrote:
> >
> > Building off Nick's idea of a system python vs a python for users to use, I
> > would see a more useful modification to be abl
-Toshio
On Mar 19, 2015 3:27 PM, "Victor Stinner" wrote:
>
> 2015-03-19 21:47 GMT+01:00 Toshio Kuratomi :
> > I think I've found the Debian discussion (October 2012):
> >
> > http://comments.gmane.org/gmane.linux.debian.devel.python/8188
> >
> >
apply to all scripts they run was
kind of lost in the followups (It wasn't directly addressed or
mentioned again.)
-Toshio
On Thu, Mar 19, 2015 at 12:27 PM, Barry Warsaw wrote:
> On Mar 19, 2015, at 11:15 AM, Toshio Kuratomi wrote:
>
>>I could see that as a difference. Ho
On Wed, Mar 18, 2015 at 2:56 PM, Barry Warsaw wrote:
> On Mar 18, 2015, at 02:44 PM, Toshio Kuratomi wrote:
>
>>Interesting, I've cautiously in favor of -s in Fedora but the more I've
>>thought about it the less I've liked -E. It just seems like PYTHONPATH is
>
On Wed, Mar 18, 2015 at 12:22:03PM -0400, Barry Warsaw wrote:
> On Mar 18, 2015, at 03:46 PM, Orion Poplawski wrote:
>
> >We're starting a discussion in Fedora about setting the default shbang for
> >system python executables and/or daemons to python -s or python -Es (or ?).
>
> We've talked abou
On Tue, Jan 07, 2014 at 09:26:20PM +0900, Stephen J. Turnbull wrote:
> Is this really a good idea? PEP 460 proposes rather different
> semantics for bytes.format and the bytes % operator from the str
> versions. I think this is going to be both confusing and a continuous
> target for "further imp
On Fri, Oct 25, 2013 at 01:32:36PM +1000, Nick Coghlan wrote:
>
> On 25 Oct 2013 09:02, "Terry Reedy" wrote:
>
> > http://lwn.net/Articles/571528/
> > https://fedoraproject.org/wiki/Changes/Python_3_as_Default
>
> Note that unlike Arch, the Fedora devs currently plan to leave "/usr/bin/
> pytho
On Tue, Oct 15, 2013 at 03:46:15PM +0200, "Martin v. Löwis" wrote:
> Am 15.10.13 14:49, schrieb Daniel Holth:
> > It is part of the ZIP specification. CP437 or UTF-8 are the two
> > official choices, but other encodings happen on Russian, Japanese
> > systems.
>
> Indeed. Formally, the other encod
On Thu, Sep 5, 2013 at 6:09 PM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
> > We're open source, and I think it benefits our mission to support open,
> > decentralized, and free systems like OpenID and Persona.
>
> Thus speaks an employee of yet another Provider-That-Won't-Accept-My-
>
On Thu, Sep 05, 2013 at 10:25:22PM +0400, Oleg Broytman wrote:
> On Thu, Sep 05, 2013 at 02:16:29PM -0400, Donald Stufft
> wrote:
> >
> > On Sep 5, 2013, at 2:12 PM, Oleg Broytman wrote:
> > > I used to use myOpenID and became my own provider using poit[1].
> > > These days I seldom use OpenI
On Thu, Sep 05, 2013 at 02:53:43PM -0400, Barry Warsaw wrote:
>
> This probably isn't the only application of these technologies, but I've
> always thought about OAuth as delegating authority to scripts and programs to
> act on your behalf. For example, you can write a script to interact with
> L
On Thu, Jul 25, 2013 at 10:25:26PM +1000, Nick Coghlan wrote:
> On 25 July 2013 20:38, Toshio Kuratomi wrote:
> >
> > On Jul 24, 2013 6:37 AM, "Brett Cannon" wrote:
> >> The key, though, is adding python2 and getting your code to use that
> >> binary
On Jul 24, 2013 6:37 AM, "Brett Cannon" wrote:
> The key, though, is adding python2 and getting your code to use that
binary specifically so that shifting the default name is more of a
convenience than something which might break existing code not ready for
the switch.
>
Applicable to this, does
On Wed, Jul 24, 2013 at 12:42:09PM -0400, Barry Warsaw wrote:
> On Jul 25, 2013, at 01:41 AM, Nick Coghlan wrote:
>
> >How's this for an updated wording in the abstract:
> >
> > * for the time being, all distributions should ensure that python
> >refers to the same target as python2
> > * howeve
Note: I'm the opposite number to bkabrda in the discussion on the Fedora
Lists about how quickly we should be breaking end-user expectations of what
"python" means.
On Wed, Jul 24, 2013 at 09:34:11AM -0400, Brett Cannon wrote:
>
>
>
> On Wed, Jul 24, 2013 at 5:12 AM, Bohuslav Kabrda wrote:
>
On Tue, May 28, 2013 at 01:22:01PM -0400, Barry Warsaw wrote:
> On May 27, 2013, at 11:38 AM, Toshio Kuratomi wrote:
>
> >- If upstream doesn't deal with it, then we use a "python3-" prefix. This
> >matches with our package naming so it seemed to make sense.
On Sat, May 25, 2013 at 05:57:28PM +1000, Nick Coghlan wrote:
> On Sat, May 25, 2013 at 5:56 AM, Barry Warsaw wrote:
> > Have any other *nix distros addressed this, and if so, how do you solve it?
>
> I believe Fedora follows the lead set by our own makefile and just
> appends a "3" to the script
On Fri, Dec 7, 2012 at 10:46 PM, PJ Eby wrote:
>
> In any case, as I said before, I don't have an issue with the fields
> all being declared as being for informational purposes only. My issue
> is only with recommendations for automated tool behavior that permit
> one project's author to exercis
On Sun, Dec 09, 2012 at 12:48:45AM -0500, PJ Eby wrote:
>
> Do any of the distro folks know of a Python project tagged as
> conflicting with another for their distro, where the conflict does
> *not* involve any files in conflict?
>
In Fedora we do work to avoid most types of Conflicts (backportin
On Sun, Dec 09, 2012 at 01:51:09PM +1100, Chris Angelico wrote:
> On Sun, Dec 9, 2012 at 1:11 PM, Steven D'Aprano wrote:
> > Why would a software package called "Spam" install a top-level module called
> > "Jam" rather than "Spam"? Isn't the whole point of Python packages to solve
> > this namespa
On Fri, Dec 07, 2012 at 01:18:40AM -0500, PJ Eby wrote:
> On Thu, Dec 6, 2012 at 1:49 AM, Toshio Kuratomi wrote:
> > On Wed, Dec 05, 2012 at 07:34:41PM -0500, PJ Eby wrote:
> >> On Wed, Dec 5, 2012 at 6:07 PM, Donald Stufft
> >> wrote:
> >>
> >&
On Wed, Dec 05, 2012 at 07:34:41PM -0500, PJ Eby wrote:
> On Wed, Dec 5, 2012 at 6:07 PM, Donald Stufft wrote:
>
> Nobody has actually proposed a better one, outside of package renaming
> -- and that example featured an author who could just as easily have
> used an obsoleted-by field.
>
How abo
On Wed, Dec 05, 2012 at 02:46:11AM -0500, Donald Stufft wrote:
> On Wednesday, December 5, 2012 at 2:13 AM, PJ Eby wrote:
>
> On Mon, Dec 3, 2012 at 2:43 PM, Daniel Holth wrote:
>
> How to use Obsoletes:
>
> The author of B decides A is obsolete.
>
> A releases an e
On Tue, Nov 20, 2012 at 06:43:32PM -0500, Daniel Holth wrote:
> No. We trust the packages we install, including the way they decide to use
> the metadata. A bad package could delete all our files or cause dependency
> resolution to fail. Mostly they won't.
>
Agreed. And this is closer to the way
On Mon, Nov 19, 2012 at 07:49:41PM -0500, Donald Stufft wrote:
> Other languages seem to get along fine without it. Even the OS
> managers which have it don't allow it to be used to masquerade
> as another project, only to make generic virtual packages (e.g. "email").
>
I'm not sure this assertion
On Tue, Oct 16, 2012 at 11:27:24AM +0200, Antoine Pitrou wrote:
> On Tue, 16 Oct 2012 05:05:23 -0400
> Trent Nelson wrote:
> > On Tue, Oct 16, 2012 at 01:43:37AM -0700, Charles-François Natali wrote:
> > > > My understanding is that we use a specific version of autoconf.
> > > > The reason is that
On Wed, Jun 13, 2012 at 01:58:10PM -0400, R. David Murray wrote:
>
> OK, but you didn't answer the question :). If I understand correctly,
> everything you said applies to *writing* the bytecode, not reading it.
>
> So, is there any reason to not use the .pyo file (if that's all that is
> around
On Sat, Feb 11, 2012 at 04:32:56PM +1000, Nick Coghlan wrote:
>
> This would then be seen by pydoc and help(), as well as being amenable
> to programmatic inspection.
>
Would using
warnings.warn('This is a provisional API and may change radically from'
' release to release', Provi
On Thu, Jan 05, 2012 at 08:35:57PM +, Paul Moore wrote:
> On 5 January 2012 19:33, David Malcolm wrote:
> > We have similar issues in RHEL, with the Python versions going much
> > further back (e.g. 2.3)
> >
> > When backporting the fix to ancient python versions, I'm inclined to
> > turn the
On Thu, Dec 22, 2011 at 02:49:06AM +0100, Victor Stinner wrote:
>
> >Do people still have to use this in commercial environments or is
> >everyone on 2.6+ nowadays?
>
> At work, we are still using Python 2.5. Six months ago, we started a
> project to upgrade to 2.7, but we have now more urgent ta
On Tue, Nov 22, 2011 at 08:27:24PM -0800, Raymond Hettinger wrote:
>
> On Nov 22, 2011, at 7:50 PM, Larry Hastings wrote:
> > But look! I'm already practicing: NO YOU CAN'T CHECK THAT IN. How's that?
> > Needs work?
>
> You could try a more positive leadership style: THAT LOOKS GREAT, I'M SU
On Wed, Nov 23, 2011 at 01:41:46AM +0900, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
> > Hopefully, we're going to be making a dent in that in the next version of
> > Ubuntu.
>
> This is still a big mess in Gentoo and MacPorts, though. MacPorts
> hasn't done anything about ceating a t
On Tue, Oct 11, 2011 at 01:49:43PM +0100, Michael Foord wrote:
> On 10/10/2011 21:21, Giampaolo Rodolà wrote:
> >
> >Toshio Kuratomi wrote:
> >>I have a need to support a small amount of code as far back as python-2.3
> >>I don't suppose you're inter
On Tue, Oct 11, 2011 at 12:22:12AM -0400, Terry Reedy wrote:
> On 10/10/2011 4:21 PM, Giampaolo Rodolà wrote:
> >Thanks everybody for your feedback.
> >I created a gcode project here:
> >http://code.google.com/p/pycompat/
>
> This project will be easier if the test suite for a particular
> functio
I have some similar code in kitchen:
http://packages.python.org/kitchen/api-overview.html
It wasn't as ambitious as your initial goals sound (I was only working on
pulling out what was necessary for what people requested rather than an
all-inclusive set of changes). You're welcome to join me and
On Wed, Oct 05, 2011 at 06:14:08PM +0200, Antoine Pitrou wrote:
> Le mercredi 05 octobre 2011 à 18:12 +0200, "Martin v. Löwis" a écrit :
> > >> Not sure what you are using it for. If you need to extend the buffer
> > >> in case it is too small, there is absolutely no way this could work
> > >> with
On Fri, Aug 12, 2011 at 12:19:23PM -0400, Barry Warsaw wrote:
> On Aug 12, 2011, at 01:10 PM, Nick Coghlan wrote:
>
> >1. Accept the reality of that situation, and propose a mechanism that
> >minimises the impact of the resulting ambiguity on end users of Python
> >by allowing developers to be exp
On Tue, Jun 28, 2011 at 03:46:12PM +0100, Paul Moore wrote:
> On 28 June 2011 14:43, Victor Stinner wrote:
> > As discussed before on this list, I propose to set the default encoding
> > of open() to UTF-8 in Python 3.3, and add a warning in Python 3.2 if
> > open() is called without an explicit e
On Wed, Apr 06, 2011 at 11:04:08AM +0200, John Arbash Meinel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> ...
> > #. ``__version_info__`` SHOULD be of the format returned by PEP 386's
> >``parse_version()`` function.
>
> The only reference to parse_version in PEP 386 I coul
On Wed, Mar 30, 2011 at 08:36:43AM +0200, Lennart Regebro wrote:
> On Wed, Mar 30, 2011 at 07:54, Toshio Kuratomi wrote:
> > Lennart is missing that you just need to use the same encoding
> > + surrogateescape (or stick with bytes) for decoding the byte strings that
> &
On Tue, Mar 29, 2011 at 10:55:47PM +0200, Victor Stinner wrote:
> Le mardi 29 mars 2011 à 22:40 +0200, Lennart Regebro a écrit :
> > The lesson here seems to be "if you have to use blacklists, and you
> > use unicode strings for those blacklists, also make sure the string
> > you compare with doesn
On Tue, Mar 29, 2011 at 07:23:25PM +0100, Michael Foord wrote:
> Hey all,
>
> Not sure how real the security risk is here:
>
> http://blog.omega-prime.co.uk/?p=107
>
> Basically he is saying that if you store a list of blacklisted files
> with names encoded in big-5 (or some other non-utf8
On Mon, Mar 21, 2011 at 09:06:22PM -0400, David Malcolm wrote:
>
> Other ideas that occur:
> - does rpmlint check for encoding yet?
> - what to do e.g. about canonicalization? What happens if one rpm
> provide a feature named "café" (where the "é" is U+00E9) and another rpm
> requires a featu
On Fri, Mar 18, 2011 at 07:40:43PM -0700, Guido van Rossum wrote:
> On Fri, Mar 18, 2011 at 7:28 PM, Greg Ewing
> wrote:
> > Tres Seaver wrote:
> >
> >> I'm not even sure why you would want __version__ in 99% of modules: in
> >> the ordinary cases, a module's version should be either the Python
On Tue, Mar 08, 2011 at 06:43:19PM -0800, Glenn Linderman wrote:
> On 3/8/2011 12:02 PM, Terry Reedy wrote:
>
> On 3/7/2011 9:31 PM, Reliable Domains wrote:
>
>
> The launcher need not be called "python.exe", and maybe it would be
> better called #@launcher.exe (or similar, d
On Tue, Mar 08, 2011 at 08:25:50AM +1000, Nick Coghlan wrote:
> On Tue, Mar 8, 2011 at 1:30 AM, Barry Warsaw wrote:
> > On Mar 04, 2011, at 12:00 PM, Toshio Kuratomi wrote:
> >
> >>Actually, my post was saying that these two can be decoupled. ie: It's
> >&g
On Fri, Mar 04, 2011 at 12:56:16PM -0500, Fred Drake wrote:
> On Fri, Mar 4, 2011 at 12:35 PM, Michael Foord
> wrote:
> > That (below) is not distutils it is setuptools. distutils just uses
> > `scripts=[...]`, which annoyingly *doesn't* work with setuptools.
>
> Right; distutils scripts are just
On Fri, Mar 04, 2011 at 01:56:39PM -0500, Barry Warsaw wrote:
>
> I don't agree that /usr/bin/python should not be installed. The draft PEP
> language hits the right tone IMHO, and I would favor /usr/bin/python pointing
> to /usr/bin/python2 on Debian, but primarily used only for the interactive
On Thu, Mar 03, 2011 at 09:46:23PM -0500, Barry Warsaw wrote:
> On Mar 03, 2011, at 09:08 AM, Toshio Kuratomi wrote:
>
> >Thinking outside of the box, I can think of something that would satisfy
> >your requirements but I don't know how appropriate it is for upstream python
On Thu, Mar 03, 2011 at 09:11:40PM -0500, Barry Warsaw wrote:
> On Mar 03, 2011, at 02:17 PM, David Malcolm wrote:
>
> >On a related note, we have a number of scripts packaged across the
> >distributions with a shebang line that reads:
> > #!/usr/bin/env python
> >which AIUI follows upstream rec
On Thu, Mar 03, 2011 at 09:55:25AM +0100, Piotr Ożarowski wrote:
> [Guido van Rossum, 2011-03-02]
> > On Wed, Mar 2, 2011 at 4:56 AM, Piotr Ożarowski wrote:
> > > [Sandro Tosi, 2011-03-02]
> > >> On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski wrote:
> > >> > I co-maintain with Matthias a package t
On Wed, Mar 02, 2011 at 01:14:32AM +0100, "Martin v. Löwis" wrote:
> > I think a PEP would help, but in this case I would request that before
> > the PEP gets written (it can be a really short one!) somebody actually
> > go out and get consensus from a number of important distros. Besides
> > Barry
On Wed, Jan 26, 2011 at 11:12:02AM +0100, "Martin v. Löwis" wrote:
> Am 26.01.2011 10:40, schrieb Victor Stinner:
> > Le lundi 24 janvier 2011 à 19:26 -0800, Toshio Kuratomi a écrit :
> >> Why not locale:
> >> * Relying on locale is simply not portable
On Wed, Jan 26, 2011 at 11:24:54AM +0900, Stephen J. Turnbull wrote:
> Toshio Kuratomi writes:
>
> > On Linux there's no defined encoding that will work; file names are just
> > bytes to the Linux kernel so based on people's argument that the convention
> > i
On Tue, Jan 25, 2011 at 10:22:41AM +0100, Xavier Morel wrote:
> On 2011-01-25, at 04:26 , Toshio Kuratomi wrote:
> >
> > * If you can pick a set of encodings that are valid (utf-8 for Linux and
> > MacOS
>
> HFS+ uses UTF-16 in NFD (actually in an Apple-specific var
On Thu, Jan 20, 2011 at 03:27:08PM -0500, Glyph Lefkowitz wrote:
>
> On Jan 20, 2011, at 11:46 AM, Guido van Rossum wrote:
> Same here. *Most* code will never be shared, or will only be shared
> between users in the same community. When it goes wrong it's also a
> learning opportunity.
On Thu, Jan 20, 2011 at 01:43:03PM -0500, Alexander Belopolsky wrote:
> On Thu, Jan 20, 2011 at 12:44 PM, Toshio Kuratomi wrote:
> > .. My examples that you're replying to involve two "properly
> > configured" OS's. The Linux workstations are configured with a
On Thu, Jan 20, 2011 at 12:51:29PM +0100, Victor Stinner wrote:
> Le mercredi 19 janvier 2011 à 20:39 -0800, Toshio Kuratomi a écrit :
> > Teaching students to write non-portable code (relying on filesystem encoding
> > where your solution is, don't upload to pypi anythin
On Wed, Jan 19, 2011 at 09:02:17PM -0800, Glenn Linderman wrote:
> On 1/19/2011 8:39 PM, Toshio Kuratomi wrote:
>
> use this::
>
>import cafe as café
>
> When you do things this way you do not have to translate between unknown
> encodings into unicod
On Thu, Jan 20, 2011 at 03:51:05AM +0100, Victor Stinner wrote:
> For a lesson at school, it is nice to write examples in the
> mother language, instead of using "raw" english with ASCII identifiers
> and filenames.
Then use this::
import cafe as café
When you do things this way you do not hav
On Thu, Jan 20, 2011 at 01:26:01AM +0100, Victor Stinner wrote:
> Le mercredi 19 janvier 2011 à 15:44 -0800, Toshio Kuratomi a écrit :
> > Additionally, many unix filesystem don't specify a filesystem encoding for
> > filenames; they deal in legal and illegal bytes
On Wed, Jan 19, 2011 at 07:11:52PM -0500, James Y Knight wrote:
> On Jan 19, 2011, at 6:44 PM, Toshio Kuratomi wrote:
> > This problem of which encoding to use is a problem that can be
> > seen on UNIX systems even now. Try this:
> >
> > echo 'print("hi
On Wed, Jan 19, 2011 at 04:40:24PM -0500, Terry Reedy wrote:
> On 1/19/2011 4:05 PM, Simon Cross wrote:
>
> >I have no problem with non-ASCII module identifiers being valid
> >syntax. It's a question of whether attempting to translate a non-ASCII
>
> If the names are the same, ie, produced with t
On Fri, Dec 03, 2010 at 11:52:41PM +0100, "Martin v. Löwis" wrote:
> Am 03.12.2010 23:48, schrieb Éric Araujo:
> >> But I'm not interested at all in having it in distutils2. I want the
> >> Python build itself to use it, and alas, I can't because of the freeze.
> > You can’t in 3.2, true. Neither
On Wed, Dec 01, 2010 at 10:06:24PM -0500, Alexander Belopolsky wrote:
> On Wed, Dec 1, 2010 at 9:53 PM, Terry Reedy wrote:
> ..
> > Does Sphinx run on PY3 yet?
>
> It does, but see issue10224 for details.
>
> http://bugs.python.org/issue10224
>
Also, docutils has an unported module.
/me needs
On Tue, Nov 09, 2010 at 01:49:01PM -0500, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/08/2010 06:26 PM, Bobby Impollonia wrote:
>
> > This does hurt because anyone who was relying on "import *" to get a
> > name which is now omitted from __all__ is going to upgr
On Tue, Nov 09, 2010 at 11:46:59AM +1100, Ben Finney wrote:
> Ron Adam writes:
>
> > def _publicly_documented_private_api():
> > """ Not sure why you would want to do this
> > instead of using comments.
> > """
> > ...
>
> Because the docstring is available at the interpret
On Fri, Oct 29, 2010 at 11:12:28AM -0700, geremy condra wrote:
> On Thu, Oct 28, 2010 at 11:55 PM, Glyph Lefkowitz
> > Let's take PyPI numbers as a proxy. There are ~8000 packages with a
> > "Programming Language::Python" classifier. There are ~250 with "Programming
> > Langauge::Python::3". Rou
On Thu, Oct 21, 2010 at 12:00:40PM -0400, Barry Warsaw wrote:
> On Oct 20, 2010, at 02:11 AM, Victor Stinner wrote:
>
> >I plan to fix Python documentation: specify the encoding used to decode all
> >byte string arguments of the C API. I already wrote a draft patch: issue
> >#9738. This lack of
On Fri, Oct 08, 2010 at 05:12:44PM +0200, Antoine Pitrou wrote:
> On Fri, 8 Oct 2010 11:04:35 -0400
> Toshio Kuratomi wrote:
> >
> > In the larger universe of programs, it might make for more intuitive
> > remembering of the command to use a prefix (either py or python)
On Fri, Oct 08, 2010 at 10:26:36AM -0400, Barry Warsaw wrote:
> On Oct 08, 2010, at 03:22 PM, Tarek Ziadé wrote:
>
> >Yes that what I was thinking about -- I am not too worried about this,
> >since every Linux deals with the 'more than one python installed'
> >case.
>
> Kind of. but anyway...
On Wed, Sep 29, 2010 at 01:23:24PM -0700, Guido van Rossum wrote:
> On Wed, Sep 29, 2010 at 1:12 PM, Brett Cannon wrote:
> > On Wed, Sep 29, 2010 at 12:03, Guido van Rossum wrote:
> >> A problem with that is that we regularly make matching improvements to
> >> upload.py and the server-side code i
On Thu, Sep 16, 2010 at 10:56:56AM -0700, Guido van Rossum wrote:
> On Thu, Sep 16, 2010 at 10:46 AM, Martin (gzlist)
> wrote:
> > On 16/09/2010, Guido van Rossum wrote:
> >>
> >> In all cases I can imagine where such polymorphic functions make
> >> sense, the necessary and sufficient assumption
On Thu, Sep 16, 2010 at 09:52:48AM -0400, Barry Warsaw wrote:
> On Sep 16, 2010, at 11:28 PM, Nick Coghlan wrote:
>
> >There are some APIs that should be able to handle bytes *or* strings,
> >but the current use of string literals in their implementation means
> >that bytes don't work. This turns
On Fri, Aug 13, 2010 at 03:15:28AM +0200, Éric Araujo wrote:
> > A good alternative would be to make the config file overridable. That way
> > you can have sysconfig.cfg next to sysconfig.py or in a known config
> > directory relative to the python stdlib install but also let the
> > distributions
On Fri, Aug 13, 2010 at 07:48:22AM +1000, Nick Coghlan wrote:
> 2010/8/12 Éric Araujo :
> >> Choosing an arbitrary location we think is good on every system is fine
> >> and non risky I think, as long as Python let the various distribution
> >> change those paths though configuration.
> >
> > Don’t
On Tue, Jul 06, 2010 at 10:10:09AM +0300, Nir Aides wrote:
> I take "...running off with the good stuff and selling it for profit" to mean
> "creating derivative work and commercializing it as proprietary code" which
> you
> can not do with GPL licensed code. Also, while the GPL does not prevent
On Wed, Jun 23, 2010 at 11:35:12PM +0200, Antoine Pitrou wrote:
> On Wed, 23 Jun 2010 17:30:22 -0400
> Toshio Kuratomi wrote:
> > Note that this assumption seems optimistic to me. I started talking to
> > Graham
> > Dumpleton, author of mod_wsgi a couple years back be
1 - 100 of 170 matches
Mail list logo
