e this would break is astronomical.
--
Stephen Hansen
m e @ i x o k a i . i o
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
to do basically anything, INCLUDING produce
closed source releases if someone wanted to, or just release
modifications or modules that are available under different licenses.
The OSD encompasses both ends of the spectrum: the GPL's mandate of
source access and the OSD's mandate of t
>
> Sounds great right? Everybody will be happy! So let's nail it down! If I
> was in charge, here's what I'd do:
>
> * standardise the syntax for type hints in 3.5, as per PEP484
> * but: recommend the use of stub files as the preferred place to store
> hints
> * and: deprecate function annotati
On Mon, Aug 4, 2014 at 12:12 AM, Larry Hastings wrote:
>
> Several people have said they found the name "nullable" surprising,
> suggesting I use another name like "allow_none" or "noneable". I, in turn,
> find their surprise surprising; "nullable" is a term long associated with
> exactly this c
that happen to be 7-bit ascii-compatible and can't perform text-ish
operations on them--
Python 3.3.3 (v3.3.3:c3896275c0f6, Nov 18 2013, 21:18:40) [MSC v.1600 32
bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more informa
On Sun, Apr 7, 2013 at 6:53 AM, Christian Tismer wrote:
> On 07.04.13 14:10, Skip Montanaro wrote:
>
> Where I work (a trading firm that uses Python as just one of many
> different pieces of technology, not a company where Python is the core
> technology upon which the firm is based) we are only
') isn't supported on Windows XP, I'll be very sad, and will have
to be stuck on Python 3.x-1 for .. awhile, where "awhile" is out of my
control and up to the Masses who are unable or can't be bothered with
fixing what works for them w/ WinXP.
--
Stephen Hansen
comfortable opening up such access except on a
person-by-person/case-by-case basis.
I idle on #python-dev as "ixokai" -- you can ping me there and I
generally wake up rather promptly. That, or email works too.
--
Stephen Hansen
... Also: Ixokai
... Mail: me+python
he whole visual studio environment set up.
I have computing resources, cycles, and time that's free to offer up:
but the differing responses here makes me unsure if I'm being useful or
not in trying here :)
--
Stephen Hansen
... Also: Ixokai
... Mail: me+python (
e, but this again
> is more complicated).
Oh! Well if it takes a paid version of VS, then I won't be able to do
it. I'll experiment with getting the SDK and using that and seeing if I
can make it work.
--
Stephen Hansen
... Also: Ixokai
... Mail: me+python (AT) ixokai (D
On 10/13/10 3:14 PM, "Martin v. Löwis" wrote:
> Am 14.10.2010 00:08, schrieb Stephen Hansen:
>> On 10/13/10 2:47 PM, Antoine Pitrou wrote:
>>> (you'll notice that we have currently no 64-bit Windows machine although
>>> 64-bit support under Windows has
ildslave on. Despite being a VM
it gets ownership of two cores and 4 gigs of RAM, so should be plenty
fast to handle the load. And I do run it 24/7.
--
Stephen Hansen
... Also: Ixokai
... Mail: me+python (AT) ixokai (DOT) io
... Blog: http://meh.ixokai.io/
signature.asc
Description: Open
On Fri, Oct 8, 2010 at 11:09 AM, Stephen Hansen
> wrote:
> On Fri, Oct 8, 2010 at 10:28 AM, Antoine Pitrou wrote:
>
>> On Fri, 8 Oct 2010 10:02:59 -0700
>> Stephen Hansen > wrote:
>> >
>> > And long story short, it gets to 201 and runs test_cmd_line
On Fri, Oct 8, 2010 at 10:28 AM, Antoine Pitrou wrote:
> On Fri, 8 Oct 2010 10:02:59 -0700
> Stephen Hansen > wrote:
> >
> > And long story short, it gets to 201 and runs test_cmd_line in the same
> > order as the buildbot did, and it succeeds too, and I curse the go
I'm sure this has to be my configuration somehow, but I'm getting a build
failure that I don't quite know how to debug, because I can't reproduce it
when I run the test manually. Any advice would be appreciated-- I'm a
buildslave newbie :-)
I'm referring to
http://www.python.org/dev/buildbot/build
On Fri, Oct 8, 2010 at 8:00 AM, Antoine Pitrou wrote:
>
> Hi,
>
> > The failure is happening just because it can't possibly succeed, I set
> > up the account for the buildbot in such a way that it has no access to
> > a GUI context. I'm going to rectify that today so I can properly test
> > TK.
>
On Fri, Oct 8, 2010 at 2:42 AM, Antoine Pitrou wrote:
> On Tue, 5 Oct 2010 10:08:59 -0700
> Stephen Hansen wrote:
> > On Sat, Oct 2, 2010 at 1:37 PM, "Martin v. Löwis" >wrote:
> >
> > > > I'm already running a Jython buildslave on an Intel Ma
On Sat, Oct 2, 2010 at 1:37 PM, "Martin v. Löwis" wrote:
> > I'm already running a Jython buildslave on an Intel Mac Pro which is
> > pretty underused - I'd be happy to run a CPython one there too, if
> > it'd be worthwhile.
>
> I think Bill was specifically after Snow Leopard - what system are yo
On Sun, Jul 11, 2010 at 4:53 PM, Steve Holden wrote:
> Stephen Hansen wrote:
> > On Sat, Jul 10, 2010 at 9:23 PM, Guilherme Polo > <mailto:ggp...@gmail.com>> wrote:
> >
> > By "never had a problem" do you mean using some of the latest
> vers
On Sat, Jul 10, 2010 at 9:23 PM, Guilherme Polo wrote:
> By "never had a problem" do you mean using some of the latest versions
> ? Here, running "idle" from a mac terminal and trying to type: print
> "hi" crashes when entering the quotation mark.
Huh? Works fine for me. Python 2.6.1, OSX 10.6.
>
> You can't even print them without getting an error from Python. In fact,
> you also can't print strings containing the proposed half-surrogate
> encodings either: in both cases, the output encoder rejects them with a
> UnicodeEncodeError. (If not even Python, with its generally lenient
> att
> But my point is that we we need to focus on finding real use cases and
> exploring how best to solve them. Otherwise we might as well throw in
> my OrderedSet[1] as-is, despite that it's got no comments and no
> ratings. Even I don't seem to use it.
>
I'm mostly lurking on these threads, so as
>
> > > IMHO, the main system without a package manager is Windows.
> >
> > AFAICT the MacOS platform also lacks in this area.
>
> Actually, they both have them. Windows has Cygwin (rpm-based), while
> for MacOS Fink (deb-based), MacPorts (FreeBSD ports-like), and
> NetBSD's pkgsrc are all viab
(The lurker awakes...)
> > If not that I suggest something like __inject_builtins__. This
> > implies it's a command to eval/exec, and doesn't necessarily reflect
> > your current builtins (which are canonically accessible as an
> > attribute of your frame.)
>
> You're misunderstanding the reason
The kind of errors I mentioned ("permission denied" errors that
seem to occur without an obvious reason) have cost me at least
two weeks of debugging the hard way (with ProcessExplorer etc)
and caused my manager to loose his trust in Python at all...
I think it is well worth the effort to keep th
Anthony Baxter said that the patch wasn't making it into 2.5.1, and
since he is the release manager, his word is just about as final as
Guido's (at least regarding the releases he does).
Ah, oops! Work got busy, and I must have missed that in the Endless Threads.
Nevermind then. :)
--S
__
I'm sure everyone remembers the big ol' honking discussion on the change to
os.splitext; it sorta fizzled after Guido asked if people would accept a
pronouncement on the subject. I'm not anyone in the Python world, but felt
strongly enough on the particular subject to submit a patch (and later
rev
That may actually be a genuinely useful approach:
splitext(name, ignore_leading_dot=False, all_ext=False)
... that's perfect. I updated my patch to do it that way! :)
--S
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
be my second contribution ever. And the first one to be more
then a line and a half :P
--
Stephen Hansen
Development
Advanced Prepress Technology
[EMAIL PROTECTED]
(818) 748-9282
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/ma
For example, I committed a fix for urllib that made it raise IOError
instead
of an AttributeError (which wasn't explicitly raised, of course) if a
certain
error condition occurs.
This is changed behavior too, but if we are to postpone all these fixes
to 3.0, we won't have half of the fixes in Pyt
I'm a long-term lurker and Python coder, and although I've never really
contributed much to the list, I do make a point to keep up on it so I'm
prepared at least when changes come through. This thread's gone on forever,
so I thought I'd offer my opinion :) Mwha.
Ahem.
First of all, I think the c
31 matches
Mail list logo
