Russell E. Owen wrote:
> In article ,
> Raymond Hettinger wrote:
>
> > On Sep 14, 2013, at 1:32 PM, Ned Deily wrote:
> > > The
> > > most recent Developer Tools for 10.8 and 10.7 systems, Xcode 4.6.x, have
> > > a mature clang but do not provide a 10.6 SDK. Even with using an SDK,
> > >
Russell Owen wrote:
> I agree that a policy is a good idea, and I suggest it be primarily based on
> age, since we cannot assume Apple will release new versions of the OS on a
> given timeline.
>
> I personally think too early to drop support for MacOS X 10.6 and am on the
> edge about 10.5.
Dan Mahn wrote:
> 3) Regarding the following code fragment in urlencode():
>
>k = quote_plus(str(k))
> if isinstance(v, str):
>v = quote_plus(v)
>l.append(k + '=' + v)
>elif isinstance(v, str):
># is there a reason
Bill Janssen wrote:
> Dan Mahn wrote:
>
> > 3) Regarding the following code fragment in urlencode():
> >
> >k = quote_plus(str(k))
> > if isinstance(v, str):
> >v = quote_plus(v)
> >l.append(k +
Guido van Rossum wrote:
> On Wed, Mar 4, 2009 at 10:51 AM, Jean-Paul Calderone
> wrote:
> > On Wed, 4 Mar 2009 10:46:28 -0800, Guido van Rossum
> > wrote:
> >>
> >> On Wed, Mar 4, 2009 at 10:27 AM, Jean-Paul Calderone
> >> wrote:
> >> [snip]
> >>>
> >>> So, as a disinterested party in this sp
Josiah Carlson wrote:
> On Thu, Mar 5, 2009 at 12:46 PM, Greg Ewing
> wrote:
> > Daniel Stutzbach wrote:
> >
> >> If you have a working select(), it will tell you the sockets on which
> >> read() and write() won't block, so non-blocking reads and writes are not
> >> necessary.
> >
> > No, but t
Aahz wrote:
> On Sat, Mar 07, 2009, Dan Mahn wrote:
> >
> > After a harder look, I concluded there was a bit more work to be done,
> > but still very basic modifications.
> >
> > Attached is a version of urlencode() which seems to make the most sense
> > to me.
> >
> > I wonder how I could of
Martin v. Löwis wrote:
> > If a library is well maintained then there seems to be little point in
> > moving it into the standard library as it may actually be harder to
> > maintain
>
> It depends. For quickly evolving libraries, it might be harder to
> maintain them in the core, as you can't r
Martin v. Löwis wrote:
> then there are the two (?) free-commercial
> distributions (ActivePython, and EPD).
Apple's system Python seems to qualify; it comes with a huge additional
library, including numpy and Twisted.
Bill
___
Python-Dev mailing list
Dan Mahn wrote:
> Yes, that was a good idea. I found some problems, and attached a new
> version. It looks more complicated than I wanted, but it is a very
> regular repetition, so I hope it is generally readable.
That's great, but I was hoping for more tests in lib/test/test_urllib.py.
Bill
Aahz wrote:
> Second, please follow the advice to put ALL patches on the tracker.
I don't care about top-posting, but I second the Second point. Let's move this
thread to the issue tracker.
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http:
Barry Warsaw wrote:
> Anyway, aside from that decision, I haven't come up with an
> elegant way to allow /output/ in both bytes and strings (input is I
> think theoretically easier by sniffing the arguments).
Probably a good thing. It just promotes more confusion to do things
that way, IMO.
Barry Warsaw wrote:
> In that case, we really need the
> bytes-in-bytes-out-bytes-in-the-chewy-
> center API first, and build things on top of that.
Yep.
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/py
Mart Sõmermaa wrote:
> On Sun, Apr 19, 2009 at 2:06 AM, Nick Coghlan wrote:
> > That said, I'm starting to wonder if an even better option may be to
> > just drop the kwargs support from the function and require people to
> > always supply a parameters dictionary. That would simplify the signatu
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > Or even better, stop trying to use a mapping, and just make the "params"
> > value a list of (name, value) pairs.
>
> You can even accept both a list of (name, value) pairs /and/ some **kwa
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > This whole discussion seems a bit "rare and obscure" to me. I've built
> > URLs for years without this method, and never felt the lack. What bugs me
> > is the lack of a way to build m
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > ``The content type "application/x-www-form-urlencoded" is inefficient
> > for sending large quantities of binary data or text containing non-ASCII
> > characters.
>
> The fact that it&
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > Sure. But nowhere does a spec say that this page charset should be used
> > in sending the values of a FORM using application/x-www-form-urlencoded
> > in a new HTTP request. It's just a conve
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > Sure. And if HTTP was all about browsers keying off pages, that would
> > be fine with me. But it's not. HTTP is used in lots of places where
> > there are no browsers;
>
> I'm sorr
Hi, Christian.
Christian Schubert wrote:
> I've created an alternative profiler module which queries per-thread
> CPU usage via netlink/taskstats, which limits the applicability to
> Linux (which shouldn't be much of an issue, profiling is usually not
> done by end users).
A surprisingly large
Nick Coghlan wrote:
> Settling on 18 months would probably work though - those that crave
> stability can then use every alternate version and only upgrade every 3
> years
I wonder about that. Lots of people are forced to upgrade by new
language features: decorators, list comprehensions, set li
R. David Murray wrote:
> Both approaches are valid, but lead to different design decisions.
> I don't see any reason why both needs cannot be met by a common API,
> but I'm wondering if any existing package is going to incorporate both
> approaches satisfactorily. As another poster said, each pa
Ben Finney wrote:
> Terry Reedy writes:
>
> > I watched and was greatly impressed by the video demo of Google's new
> > Wave collaborative communication system. I believe it would/will help
> > with some of the chronic problems we (and others) have.
>
> I watched that too. It appears to be hea
Devin Cook wrote:
> Also, I have looked through the docs and code, but haven't been able to
> figure out exactly what is included in certificate "validation". Is it just
> validating the chain? Does it check the NotBefore and NotAfter dates?
I believe so, but you'll have to check the OpenSSL cod
Bill Janssen wrote:
> > Does it check that the host the socket is connected to is the same as
> > what's given in the CN field in the certificate?
>
> No. That, in general, doesn't work very well. The IETF working group
> on this is considering deprecating put
Martin v. Löwis wrote:
> FWIW, I actually don't know the answer for sure, either, so I would have
> to research this myself, too. In any case, _ssl.c is *not* the place
> where any of the certificate validation actually happens - nor does it
> happen elsewhere in the Python source code, IIUC.
St
I think if you check the issue tracker, there's already a patch for this
somewhere, IIRC.
Bill
Devin Cook wrote:
> Ok, thanks for all the feedback. Just for clarity, I'll summarize
> everything as I understand it:
>
> * OpenSSL does the all validation of the certificate itself.
> (http://opens
Thanks, Chris. Can you explain why you want to set the cipher list
explicitly? IMO, it's usually better to select a security scheme (TLS1,
or SSLv3, etc.), and let the implementation pick the cipher list.
Bill
Chris Frantz wrote:
> Done.
>
> Attached to Issue 3597, which is a similar request
data transfer over the connection.
>
> --Chris
>
>
>
> On Thu, Sep 10, 2009 at 12:09 PM, Bill Janssen wrote:
> > Thanks, Chris. Can you explain why you want to set the cipher list
> > explicitly? IMO, it's usually better to select a security scheme (TLS1,
is a good idea.
Bill
Heikki Toivonen wrote:
> Bill Janssen wrote:
> > OK, seems reasonable. Thanks. In the near term, can you do this with
> > M2Crypto or PyOpenSSL?
> >
> > When I started this update in 2007, we were trying to keep the API
> > simple to avoid
Oleg Broytmann wrote:
> On Fri, Sep 04, 2009 at 04:02:39PM +0100, Chris Withers wrote:
> > So, httplib does this:
> >
> > GET / HTTP/1.1
> [skip]
> > While wget does this:
> >
> > GET / HTTP/1.0
> [skip]
> > - Apache responds with a chunked response only to httplib. Why is that?
>
>Probably
qwavel wrote:
> What about this bug:
> http://bugs.python.org/issue3890
> It appears to me that the SSL module is broken in the 2.6.x line on all
> platforms in one of its most common uses (non-blocking). It also seems that
> the problem and solution are well understood, so the solution would ma
Scott Dial wrote:
> Scott Dial wrote:
> > While this code is present in
> > older versions of python, it seems to have become a problem recently
> > (2009-05-06 is the earliest report on the issue) perhaps due to a
> > version bump of OpenSSL? I never noticed the problem in python2.5 even
> > tho
Bruno Harbulot wrote:
> Hello,
>
> I would like to ask a few questions and suggestions regarding the ssl
> module (in Python 2.6). (I gather from [1] that there is some effort
> going on to enhance the ssl API, but I'm not sure if this is the right
> place to discuss it.)
>
> Is there a place w
> David Lyon preisshare.net> writes:
> >
> > > This has nothing to do with pushing 3.x, but all with managing
> > > available manpower and still providing quality software.
> >
> > Python 3.x needs more carrots.
I'd be happy to move UpLib to Python 3, when the various packages that I
need are a
Reid Kleckner wrote:
> On Wed, Jan 20, 2010 at 8:14 PM, Terry Reedy wrote:
> > If CPython development moves to distributed hg, the notion of 'blessed'
> > branches (other than the PSF release branch) will, as I understand it,
> > become somewhat obsolete. If you make a branch publicly available,
s...@pobox.com wrote:
>
> Jesse>
> http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html
>
> Without reading that I can assure you that not everybody has drunk the Java
> Kool-Aid. Just because Sun thought it was a fine term doesn't mean everyone
> else will. I've been a
http://home.pipeline.com/~hbaker1/Futures.html (1977)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Cameron Simpson wrote:
> Currently all the above is somewhat "batchy"; the client end looks like
> an archiving command line tool, but it's intended to have a FUSE mode to
> present the archive as a filesystem; that I can imagine tripping over
> this issue as a user uses the filesystem for "stuff
Antoine Pitrou wrote:
> Le Sun, 14 Mar 2010 12:37:48 PDT,
> Bill Janssen a écrit :
> >
> > The old GIL is causing me a great deal of grief. My server is heavily
> > threaded, and when I get a number of Python 2.6 threads doing layout
> > analysis, my 4 and
Martin v. Löwis wrote:
> > If it's lurking behind a filesystem interface or in its daemon mode
> > (remote archive store), multiple client processes can be using it at once,
> > and it will be processing multiple tasks somewhat in parallel. Here one
> > can get a compute bound thread answering on
Ned Deily wrote:
> In article <4bc54f4f.4090...@v.loewis.de>,
> "Martin v. Lowis" wrote:
>
> > > Wasn't that problem fixed weeks ago? The installer image has been
> > > available there since several days after the release. And the link
> > > seems fine now.
> >
> > The inherent problem re
Michael Foord wrote:
> Building the Mac installer requires volunteer time which I'm not sure
> that more hardware will fix - compiling a full build of Python for Mac
> OS X (with all the Python modules like Tkinter etc) requires expertise
> which only a few people have.
That's nuts. Why isn't t
Michael Foord wrote:
> > Isn't that just a matter of having the recipe written down somewhere?
> >
>
> Yes, that would be nice. :-) Preferably a recipe that doesn't involve
> Macports or Fink which some of us are allergic to.
Yes, ditto the MacPorts/Fink allergy.
All we need is a script, r
Michael Foord wrote:
> On 14/04/2010 18:49, Steve Holden wrote:
> > Bill Janssen wrote:
> >
> >> Michael Foord wrote:
> >>
> >>
> >>>> Isn't that just a matter of having the recipe written down somewhere?
> >>>
s...@pobox.com wrote:
>
> Ronald> Creating the Mac installer is easy: just run
> Ronald> Mac/BuildScript/build-installer.py on an OSX 10.5 system where a
> Ronald> local version of Tcl/Tk 8.4 is installed in
> Ronald> /Library/Frameworks. The system should also not have fink or
>
Martin v. Löwis wrote:
> > I'd be happy to help where I can, too. All my automated testing of
> > UpLib (Windows, Ubuntu, Fedora, OS X) is done on Apple servers running
> > OS X and VirtualBox and Hudson, so I've got some experience there.
>
> Would you be interested in operating a build slave?
Martin v. Löwis wrote:
> > Michael Foord wrote:
> >
> >> Building the Mac installer requires volunteer time which I'm not sure
> >> that more hardware will fix - compiling a full build of Python for Mac
> >> OS X (with all the Python modules like Tkinter etc) requires expertise
> >> which only
s...@pobox.com wrote:
> Now that I think about it, it might not be sufficient to just hide those
> directories from the environment. The Python setup.py file has
> unconditional hard-coded references to /sw, /opt/local and /usr/local. That
I added that to my virus scanner: check any setup.py fi
Ned Deily wrote:
> In article <19399.11323.946604.992...@montanaro.dyndns.org>,
> s...@pobox.com wrote:
>
> > Ned> Any idea what type of machine it is and where it is currently
> > Ned> located?
> >
> > I seem to recall it is/was a G4 XServe. My guess as to location would be at
> > xs
Ronald Oussoren wrote:
> As Antoine noted the test failures are unexpected, could you check if
> the tests pass if you do the build and testrun manually?
I'll have to fiddle with where it "is" on our network to do that. I'll
take it down and move it to different subnet.
What about this error?
Michael Foord wrote:
> Well - I have nine failing tests on trunk for Mac OS X with Snow Leopard.
>
> 9 tests failed:
> test_cmd_line test_imp test_import test_posix test_pydoc
> test_runpy test_urllib2 test_urllib2_localnet test_warnings
>
> I believe that Victor has ensured that the bu
Antoine Pitrou wrote:
> R. David Murray bitdance.com> writes:
> >
> > On Thu, 29 Apr 2010 11:28:47 -0700, Bill Janssen wrote:
> > > 8 skips unexpected on darwin:
> > > test_aepack test_applesingle test_gdb test_macos test_macostools
> &g
I've got parc-tiger-1 up and running again. It's failing on test_tk,
which makes sense, because it's running as a background twisted process,
and thus can't access the window server. I should configure that out.
I'm looking for documentation on how to configure the build slave so
that it skips t
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > I've got parc-tiger-1 up and running again. It's failing on test_tk,
> > which makes sense, because it's running as a background twisted process,
> > and thus can't access the window server.
>
> I
exar...@twistedmatrix.com wrote:
> On 03:17 am, jans...@parc.com wrote:
> >I've got parc-tiger-1 up and running again. It's failing on test_tk,
> > which makes sense, because it's running as a background twisted
> > process,
> >and thus can't access the window server. I should configure that out
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > Martin v. Löwis wrote:
> >
> >> Bill Janssen wrote:
> >>> I've got parc-tiger-1 up and running again. It's failing on test_tk,
> >>> which makes sense, because it's running as a bac
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > Martin v. Löwis wrote:
> >
> >> Bill Janssen wrote:
> >>> I've got parc-tiger-1 up and running again. It's failing on test_tk,
> >>> which makes sense, because it's running as a bac
Vincent Davis wrote:
> Not to interrupt you you conversation but I am interested in setting
> up a buildbot on one of my Macs. Is there any documentations or advise
> that is different from that of a linux machine? Any advise would be
> appreciated.
Assuming you mean "set up a build slave for
Ronald Oussoren wrote:
> Bill: could you please file an issue for this in the python tracker,
http://bugs.python.org/issue8716
> it should be possible to add a workaround for this to the Tkinter
> extension.
That would be good.
Bill
___
Python-Dev m
Antoine Pitrou wrote:
> The buildbots are sometimes subject to a flood of "svn exception"
> errors. It has been conjectured that these errors are caused by Web
> crawlers pressing "force build" buttons without filling any of the
> fields (of course, the fact that we get such ugly errors in the
>
Maciej Fijalkowski wrote:
> On Sat, May 15, 2010 at 12:07 PM, Antoine Pitrou wrote:
> > On Sat, 15 May 2010 17:57:28 -
> > exar...@twistedmatrix.com wrote:
> >>
> >> One thing I have noticed is that spammers find these forms and submit
> >> them with garbage. We can probably suppose that su
parc-leopard-1 (and most of the other builders) are failing the svn
checkout with the following error:
svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
`svn.python.org': Temporary failure in name resolution (http://svn.python.org)
When I log into that machine as "buildbot" a
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > parc-leopard-1 (and most of the other builders) are failing the svn
> > checkout with the following error:
> >
> > svn: PROPFIND of '/projects/python/trunk': Could not resolve hostname
> > `svn.python
Martin v. Löwis wrote:
> That's a common OSX problem/bug. Processes occasionally lose the ability
> to resolve host names. Various theories float around what's causing this
> (most commonly, people expect that a "controlling terminal" must be
> present); my theory is this:
>
> There is a Mach po
I can find no evidence that the buildbot installation process given on
the wiki will cause the buildbot slave to be restarted after a reboot of
the machine. To accomplish this, you should also undertake the work
described in
http://buildbot.net/trac/wiki/UsingLaunchd
On my Leopard slave, I cr
I'm running my buildbots in a captive firewalled subnet, and I have to
enumerate all the ports that the buildbot is allowed to open to the
outside world. Right now, I'm getting this error:
ERROR: test_connect (test.test_smtpnet.SmtpSSLTest)
I'm interested in having *something*, but I'm not particularly
interested in the 3.x branch. I expect it to be at least 5 years before
the various Python subsystems I depend on are all ported to 3.x, and I
expect it to be at least that long before I can move onto a version of
OS X that ships with
Bill Janssen wrote:
> I can find no evidence that the buildbot installation process given on
> the wiki will cause the buildbot slave to be restarted after a reboot of
> the machine. To accomplish this, you should also undertake the work
> described in
>
> http://buil
Nick Coghlan wrote:
> Bill Janssen wrote:
> > Right now, I'm faced with the prospect of Apple's next OS including
> > Python 2.7, and being saddled with the current Python 2.x terrible
> > multicore behavior for the next 5 years or so. We badly need some kind
&
Nick Coghlan wrote:
> Bill Janssen wrote:
> > As far as I'm concerned, just tying all of
> > the program's threads to a single core would be fine, though I imagine
> > others would differ.
>
> Which can be done through the OS tools for setting an application
Martin v. Löwis wrote:
> OSX doesn't really support thread affinity. The affinity API that they
> have is described on
>
> http://developer.apple.com/mac/library/releasenotes/Performance/RN-AffinityAPI/index.html
>
> You can't bind a thread to specific core with it, though, but you can
> reques
I've repeated this setup with OS X 10.4 (Tiger). Some changes to the
XML file were necessary, because I'd installed a non-system Python,
twisted, and zope.interface on this machine, and because on Tiger,
launchd daemon were not allowed to set their group ID. Here's the Tiger
version, which again
Antoine Pitrou wrote:
> On Sun, 16 May 2010 15:13:44 PDT
> Bill Janssen wrote:
> >
> > So the patch to the threading code would presumably, for those OSs where
> > the capability exists, try to put all created threads in the same
> > affinity set.
>
>
Antoine Pitrou wrote:
> Well, 2.7rc1 is scheduled in less than three weeks now. IMO any patch
> changing fundamental threading properties is a no-no (even the processor
> affinity proposal).
Unfortunately, our "fundamental threading properties" are broken for
multicore machines. And multicore s
Bill Janssen wrote:
> use it. Whether or not use explicitly know you are using threads
> (because some other package may be using them under the covers).
Of course, I meant to say, "Whether or not *youse* explicitly know you
are using threads (because some other package may be using
Antoine Pitrou wrote:
> Well, if instead of gnashing your teeth, you had contributed to the
> issue, perhaps a patch would have been committed by now (or perhaps
> not, but who knows?). If you stay silent, you cannot assume that
> someone else will stand up for *your* opinion (and the fact that n
Antoine Pitrou wrote:
> On Mon, 17 May 2010 11:15:49 PDT
> Bill Janssen wrote:
> >
> > What I did know was that
> > some of our big complicated Python multi-threaded daemons had shown
> > puzzling resource hogging when moved from small Macs to large 8-core
>
Martin v. Löwis wrote:
> > I'd hate to let a fundamental flaw like this go through simply because
> > someone somewhere somewhen set a completely synthetic deadline.
>
> No, it's not like that. We set the deadline so that we are able to
> cancel discussions like this one. It would be possible to
Terry Reedy wrote:
> On 5/17/2010 2:59 PM, Bill Janssen wrote:
> > Yes, it would. As soon as I have working 3.x versions of BeautifulSoup,
> > PIL, ReportLab, JCC, pylucene, pyglet, nltk, email, epydoc, feedparser,
> > dictclient, docutils, hachoir, mutagen, medusa,
Antoine Pitrou wrote:
> On Sun, 16 May 2010 15:13:44 PDT
> Bill Janssen wrote:
> >
> > So the patch to the threading code would presumably, for those OSs where
> > the capability exists, try to put all created threads in the same
> > affinity set.
>
> Thi
Nick Coghlan wrote:
> B. some more thought should be given to incorporating the new GIL into
> 2.7. However, this requires two things:
> - an update to the patch in 7753 to either retain the old GIL for
> platforms not supported by the new GIL or else to make the new GIL a
> configure option
>
The PPC buildbots are running pretty well, now that I've opened a few
more ports, but I'd like to find this script "pybuildbot.identify" that
they keep complaining about, and install it. I've poked around the
Python sources, but haven't found it.
Anyone know where to get it from?
Thanks.
Bill
_
Matthias Klose wrote:
> On 19.05.2010 18:09, Bill Janssen wrote:
> > The PPC buildbots are running pretty well, now that I've opened a few
> > more ports, but I'd like to find this script "pybuildbot.identify" that
> > they keep complaining abou
Martin v. Löwis wrote:
> Bill Janssen wrote:
> > Matthias Klose wrote:
> >
> >> On 19.05.2010 18:09, Bill Janssen wrote:
> >>> The PPC buildbots are running pretty well, now that I've opened a few
> >>> more ports, but I'd like to f
Martin v. Löwis wrote:
> Peter Portante wrote:
> > Does anybody think that by having problems with the new GIL that it might
> > further weaken the adoption rate for 3k? -peter
>
> No, to the contrary. By having the new GIL being superior to the old
> implementation, the adoption rate for 3k wil
Antoine Pitrou wrote:
> Le mercredi 09 juin 2010 à 12:38 +0100, Michael Foord a écrit :
> > On 09/06/2010 12:35, Antoine Pitrou wrote:
> > > On Wed, 09 Jun 2010 10:41:29 +0200
> > > "M.-A. Lemburg" wrote:
> > >
> > >> The above example will read:
> > >>
> > >> >>> b'abc'.transform("hex
Barry Warsaw wrote:
> On Jun 09, 2010, at 04:42 PM, M.-A. Lemburg wrote:
>
> >Many of them are not keen on having to maintain Python2 for much
> >longer, but some of them may have assets codified in Python2
> >or interests based Python2 that they'll want to keep for
> >more than just another 5 y
Nick Coghlan wrote:
> My personal perspective is that a lot of that code was likely already
> broken in hard to detect ways when dealing with mixed encodings -
> releasing 3.x just made the associated errors significantly easier to
> detect.
I have to agree with this, and not just about encoding
Giampaolo Rodolà wrote:
> 2010/6/17 Bill Janssen :
>
> > There's a related meta-issue having to do with antique protocols.
>
> Can I know what meta-issue are you talking about exactly?
Giampaolo, I believe that you and I have already discussed this on one
o
Considering that we've just released 2.7rc2, there are an awful lot of
red buildbots for 2.7. In fact, I don't remember having seen a green
buildbot for OS X and 2.7. Shouldn't these be fixed?
On OS X Leopard, I'm seeing failures in test_py3kwarn,
test_urllib2_localnet, test_uuid.
On OS X Tiger
Benjamin Peterson wrote:
> 2010/6/21 Bill Janssen :
> > Considering that we've just released 2.7rc2, there are an awful lot of
> > red buildbots for 2.7. In fact, I don't remember having seen a green
> > buildbot for OS X and 2.7. Shouldn't these be fixed
Antoine Pitrou wrote:
> Benjamin is not qualified to fix OS X bugs AFAIK (if you are, Benjamin,
> then sorry for misrepresenting you :-)). Actually, neither are most of
> us.
Right. I was thinking that the release manager should however be
responsible for not releasing while there are red build
Benjamin Peterson wrote:
> 2010/6/21 Bill Janssen :
> > They are at the end of the buildbot list, so off-screen if you are using
> > a normal browser. You have to scroll to see them.
>
> But not on the "stable" view and that's the only one I loo
Antoine Pitrou wrote:
> Le lundi 21 juin 2010 à 12:57 -0700, Bill Janssen a écrit :
> >
> > > Apparently some of these buildbots belong to you. Why don't you step
> > > up and investigate?
> >
> > The fact that I'm running some buildbots does
Antoine Pitrou wrote:
> OS X is only "a supported and important platform" if we have dedicated
> core developers diagnosing or even fixing issues for it (like we
> obviously have for Windows and Linux). Otherwise, I don't think we have
> any moral obligation to support it.
Fair enough.
That bei
Alexander Belopolsky wrote:
> Oh, I thought that was about http://bugs.python.org/issue8455 .
>
> On Mon, Jun 21, 2010 at 9:05 PM, Alexander Belopolsky
> wrote:
> > On Mon, Jun 21, 2010 at 6:39 PM, Paul Moore wrote:
> > ..
> >> Yes, looks like it's a bug in the test. http://bugs.python.org/iss
Alexander Belopolsky wrote:
> On Mon, Jun 21, 2010 at 9:26 PM, Bill Janssen wrote:
> ..
> > Though, isn't that behavior of urllib.proxy_bypass another bug?
>
> I don't know. Ask Ronald.
Hmmm. I brought up the System Preferences panel on my Mac, and sure
enough,
Craig Younkins wrote:
> cgi.escape never escapes single quote characters, which can easily lead to a
> Cross-Site Scripting (XSS) vulnerability. This seems to be known by many,
> but a quick search reveals many are using cgi.escape for HTML attribute
> escaping.
Did you file a bug report?
Bill
Bill Janssen wrote:
> Considering that we've just released 2.7rc2, there are an awful lot of
> red buildbots for 2.7. In fact, I don't remember having seen a green
> buildbot for OS X and 2.7. Shouldn't these be fixed?
Thanks to some action by Ronald, my two PPC OS X b
1 - 100 of 537 matches
Mail list logo
