On 23 Jun, 2010,at 04:06 PM, Alexander Belopolsky wrote:On Wed, Jun 23, 2010 at 2:08 AM, Ronald Oussoren wrote:
..
> I don't agree. The patch itself is pretty simple, but it does make a rather significant change to the build process: the
> compile-time environment in configure would be different
On Wed, Jun 23, 2010 at 2:08 AM, Ronald Oussoren wrote:
..
> I don't agree. The patch itself is pretty simple, but it does make a rather
> significant change to the build process: the
> compile-time environment in configure would be different than during the
> compilation of posixmodule. That i
On 22 Jun, 2010, at 19:05, Alexander Belopolsky wrote:
> On Tue, Jun 22, 2010 at 12:39 PM, Ronald Oussoren
> wrote:
> ..
>> Both are valid fixes, both have both advantages and disadvantages.
>>
>> Your proposal:
>> * Reverts to the behavior in 2.6
>> * Ensures that posix.getgroups and posix.set
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 buildbots are now
showing
This effectively substitutes getgrouplist called on the current user
for getgroups. In 3.x, I believe the correct action will be to
provide direct access to getgrouplist which is while not POSIX (yet?),
is widely available.
As a policy, adding non-POSIX functions to the posix module is perfectl
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, there's a checkbox, "Exclude s
On Tue, Jun 22, 2010 at 12:39 PM, Ronald Oussoren
wrote:
..
> Both are valid fixes, both have both advantages and disadvantages.
>
> Your proposal:
> * Reverts to the behavior in 2.6
> * Ensures that posix.getgroups and posix.setgroups are internally consistent
>
It is also very simple and since p
On 22 Jun, 2010, at 3:38, Alexander Belopolsky wrote:
> On Mon, Jun 21, 2010 at 6:16 PM, "Martin v. Löwis" wrote:
>>> The test_posix failure is a regression from 2.6 (but it only shows up on
>>> some machines - it is caused by a fairly braindead implementation of a
>>> couple of posix apis by Ap
On 21 Jun, 2010, at 22:25, Antoine Pitrou wrote:
> Le lundi 21 juin 2010 à 21:13 +0100, Michael Foord a écrit :
>>
>> If OS X is a supported and important platform for Python then fixing all
>> problems that it reveals (or being willing to) should definitely not be
>> a pre-requisite of provid
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.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Uns
"Martin v. Löwis" writes:
> Still, the question would be whether any of these failures can manage to
> block a release.
Exactly. Personally, I would say that in a volunteer-maintained
project, "Platform X is supported" means that "There is a bug that
seems to affect only Platform X" is a cand
On Mon, Jun 21, 2010 at 6:16 PM, "Martin v. Löwis" wrote:
>> The test_posix failure is a regression from 2.6 (but it only shows up on
>> some machines - it is caused by a fairly braindead implementation of a
>> couple of posix apis by Apple apparently).
>>
>> http://bugs.python.org/issue7900
>
> A
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
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/issue9055
>> raised.
>
> I concur. I've updat
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/issue9055
> raised.
I concur. I've updated the issue with a proposed fix. (The problem
is that proxy host names should have a '.' in them on OSX.) I am
trying to decide wheth
Paul Moore writes:
> Thanks for the alert. I've killed the stuck test and should see some
> runs going through now. Shame, really, I was getting used to seeing a
> nice page of all green results...
In my experience, my OSX and Windows buildbots need some manual TLC on
an ongoing basis. I kill o
Bill Janssen wrote:
> % make test
> [...]
> test_uuid
> test test_uuid failed -- Traceback (most recent call last):
> File "/private/tmp/Python-2.7rc2/Lib/test/test_uuid.py", line 472, in
> testIssue8621
> self.assertNotEqual(parent_value, child_value)
> AssertionError: '8395a08e40454895be5
On 21 June 2010 23:19, Paul Moore wrote:
> On 21 June 2010 22:57, Michael Foord wrote:
>>> Two of the other failures I'm pretty sure are problems in the test suite
>>> rather than bugs (as Bill said) and I'm not sure about the ctypes issue.
>>> Just starting a full build here.
>>
>> Right now I'm
On 21 June 2010 22:57, Michael Foord wrote:
>> Two of the other failures I'm pretty sure are problems in the test suite
>> rather than bugs (as Bill said) and I'm not sure about the ctypes issue.
>> Just starting a full build here.
>
> Right now I'm *only* seeing these two failures on Mac OS X (10
> There also seem to be a couple of failures left with test_gdb...
Do you mean the compiler and debugger specific issues reported in
http://bugs.python.org/issue8482?
Fixing that properly is messy, and according to Victor's last message,
even the correct conditions for skipping the test aren't co
The test_posix failure is a regression from 2.6 (but it only shows up on
some machines - it is caused by a fairly braindead implementation of a
couple of posix apis by Apple apparently).
http://bugs.python.org/issue7900
Ah, that one. I definitely think this should *not* block the release:
a) th
On 21/06/2010 22:52, Michael Foord wrote:
On 21/06/2010 22:36, "Martin v. Löwis" wrote:
Bill listed several other failures he saw on the buildbots and I see
the
same set, plus test_posix.
Still, the question would be whether any of these failures can manage
to block a release. Are they regre
On 21/06/2010 22:36, "Martin v. Löwis" wrote:
Bill listed several other failures he saw on the buildbots and I see the
same set, plus test_posix.
Still, the question would be whether any of these failures can manage
to block a release. Are they regressions from 2.6?
The test_posix failure is
Bill listed several other failures he saw on the buildbots and I see the
same set, plus test_posix.
Still, the question would be whether any of these failures can manage to
block a release. Are they regressions from 2.6? That would make them
good candidates for release blockers. Except that I
On 21/06/2010 22:12, "Martin v. Löwis" wrote:
If OS X is a supported and important platform for Python then fixing all
problems that it reveals (or being willing to) should definitely not be
a pre-requisite of providing a buildbot (which is already a service to
the Python developer community). Fi
Am 21.06.2010 21:45, schrieb Michael Foord:
On 21/06/2010 20:30, 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 lo
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
If OS X is a supported and important platform for Python then fixing all
problems that it reveals (or being willing to) should definitely not be
a pre-requisite of providing a buildbot (which is already a service to
the Python developer community). Fixing bugs / failures revealed by
Bill's buildbo
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 doesn't mean I have to fix the
> > problems that they reve
Le lundi 21 juin 2010 à 21:13 +0100, Michael Foord a écrit :
>
> If OS X is a supported and important platform for Python then fixing all
> problems that it reveals (or being willing to) should definitely not be
> a pre-requisite of providing a buildbot (which is already a service to
> the Pyth
On 21/06/2010 21:02, 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 doesn't mean I have to fix the
problems that
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 doesn't mean I have to fix the
> problems that they reveal, I think.
You certainly don't have
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 look at.
Right, and properly so.
Bill
_
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
On 21/06/2010 20:30, 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 look at.
What are the require
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 look at.
--
Regards,
Benjamin
___
Python-D
On Mon, 21 Jun 2010 12:13:05 PDT
Bill Janssen wrote:
>
> > > On OS X Leopard, I'm seeing failures in test_py3kwarn,
> > > test_urllib2_localnet, test_uuid.
> > >
> > > On OS X Tiger, I'm seeing failures in test_pep277, test_py3kwarn,
> > > test_ttk_guionly, and test_urllib2_localnet.
>
> Um -- s
On Jun 21, 2010, at 1:56 PM, 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?
>
> On OS X Leopard, I'm seeing failures in tes
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?
>
> It seems most of them are off lin
On 21 June 2010 18:56, 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?
Ack! My buildbot has looked fine, but on closer inspe
On Mon, 21 Jun 2010 10:56:59 PDT
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?
>
> On OS X Leopard, I'm seeing failures in
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?
It seems most of them are off line and there last run was just a failure
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
43 matches
Mail list logo
