Tres Seaver wrote:
> Tarek Ziadé wrote:
>> I didn't know the split story went like this. I took it like the
>> "natural" split everyone
>> agreed on, and I saw this distutils <-> Makefile link like something to fix.
>
>> So, it sounds like a bad idea now :)
>
> Parsing the Makefile at runtime see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tarek Ziadé wrote:
> On Sun, Nov 15, 2009 at 3:35 AM, Christian Heimes wrote:
> [..]
>> Do we really want to change distutils to solve a problem of a third
>> party packaging system when the problem was created by the very same
>> third party in the f
On Nov 13, 2009, at 6:23 PM, Greg Ewing wrote:
Martin v. Löwis wrote:
> Some of the Python maintainers have recently started objecting to
this
> setup, asking that the standard library should be split into
separate
> packages that are released and distributed independent of Python.
Other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
P.J. Eby wrote:
> At 09:45 AM 11/14/2009 +0100, Martin v. Löwis wrote:
>> Paul Moore wrote:
>>> 2009/11/13 Tres Seaver :
I can see the information about the poll, and a link to view the
results, without logging in.
http://pypi.pyth
Martin> It's far from obvious. It's called "provider-driven identifier
Martin> selection". PyPI redirects your browser to Google. Google looks
Martin> at the Google cookie, and finds your identity; they also see
Martin> that you have opted to automatically log into PyPI. So without
> Even not having provider changes supported would still allow me to use
> my openid with PyPI which would be great. The only problem with changing
> provider that I can see is when the provider a user changes to would
> then be a duplicate - in which case I think just refusing to allow the
> login
Martin v. Löwis wrote:
[snip...]
Why not allow users to login with their own openid, but
only allow one account to refer back to the same delegated account?
That sounds good. I'm not sure how to implement a provider change
in that scenario, though.
Even not having provider changes sup
s...@pobox.com wrote:
> Martin> That's indeed what PyPI attempts to do. At the "claim openid"
> Martin> place, follow the Launchpad link. It should guide you through
> Martin> the procedure.
>
> Well, since I use Google a lot more I'd prefer to use that. If I click the
> Google OpenID
There are non-stable buildbots that are failing consistently, but this
message is about something else. Now that the biggest stability
issues have been addressed some less-noisy stability issues are visible.
The two that I have noticed most often are test_httpsservers, which
hangs occasionally, a
Michael Foord writes:
> myopenid *does* the validation, but my registered openid is
> www.voidspace.org.uk and I *should* be able to change provider without
> creating a new account.
I'm very glad this issue is being discussed, but it's unfortunately
taking place both here (where it's off-topic)
> This doesn't seem to be a problem for all the other sites I use my
> openid with.
Perhaps they don't care about fake accounts at all? That would, in
particular, be the case if they accept arbitrary OpenID providers
(which means that essentially no real authentication happens).
> Why not allow u
Martin> That's indeed what PyPI attempts to do. At the "claim openid"
Martin> place, follow the Launchpad link. It should guide you through
Martin> the procedure.
Well, since I use Google a lot more I'd prefer to use that. If I click the
Google OpenID link I now get
OpenID is al
Martin v. Löwis wrote:
Can't you then produce hundreds of IDs, all delegating to the same
identity?
Yes.
But then, users can easily create as many fake accounts as they want to.
This is not something I want to happen (it's still possible to setup
fake accounts, but it should be mor
On Sun, Nov 15, 2009 at 2:44 PM, "Martin v. Löwis" wrote:
> But then, users can easily create as many fake accounts as they want to.
>
Why not do something more robust, then? For example, when a user enters an
OpenID that hasn't been seen by PyPi before, make them enter a CAPTCHA.
--
Daniel Stu
On Sun, Nov 15, 2009 at 05:31, Georg Brandl wrote:
> Antoine Pitrou schrieb:
>> Tarek Ziadé gmail.com> writes:
>>>
>>> This cannot work on all platforms, when our Makefile is not shipped
>>> with python but python-devel. (like Fedora)
>>
>> This practice is stupid anyway, because it means you hav
On Sun, Nov 15, 2009 at 12:38 PM, Terry Reedy wrote:
> Ezio Melotti wrote:
>>
>> Python currently accepts global statements at the top level:
>>
>> I opened an issue on the tracker (http://bugs.python.org/issue7329)
>> and Benjamin suggested to discuss this here.
>> The test he mentioned is in tes
> I've never found OpenID at all intuitive to use. Are there instructions on
> pypi.python.org which detail the steps necessary to use OpenID to login? I
> saw the "Claim OpenID" link on my PyPI profile page. So now I have an
> OpenID URL. What am I supposed to do with that? If I visit that UR
>> Can't you then produce hundreds of IDs, all delegating to the same
>> identity?
>
> Yes.
But then, users can easily create as many fake accounts as they want to.
This is not something I want to happen (it's still possible to setup
fake accounts, but it should be more difficult for the average
2009/11/15 Brett Cannon :
> On Sat, Nov 14, 2009 at 20:01, Benjamin Peterson wrote:
>> 2009/11/14 Nick Coghlan :
>>> This does constrain where we can use itertools - if we want carte
>>> blanche to use it anywhere in the standard library, even those parts
>>> that are imported as part of the build
On Sat, Nov 14, 2009 at 20:01, Benjamin Peterson wrote:
> 2009/11/14 Nick Coghlan :
>> This does constrain where we can use itertools - if we want carte
>> blanche to use it anywhere in the standard library, even those parts
>> that are imported as part of the build chain, we'll need to bite the
>
Ezio Melotti wrote:
Python currently accepts global statements at the top level:
I opened an issue on the tracker (http://bugs.python.org/issue7329)
and Benjamin suggested to discuss this here.
The test he mentioned is in test_global.py:
def test4(self):
prog_text_4 = """\
global x
x
Benjamin Peterson wrote:
2009/11/15 Michael Foord :
Well, personally I think it would be a good thing if this raised an
exception during bytecode compilation - but it would fall under the
moratorium and have to wait a few years.
It could probably be considered a bug, though, since the global
s
Martin> Then I recommend that you get a google account for your email
Martin> address, and register to PyPI using OpenID.
I've never found OpenID at all intuitive to use. Are there instructions on
pypi.python.org which detail the steps necessary to use OpenID to login? I
saw the "Claim
Benjamin Peterson python.org> writes:
>
> 2009/11/15 Michael Foord voidspace.org.uk>:
> > Well, personally I think it would be a good thing if this raised an
> > exception during bytecode compilation - but it would fall under the
> > moratorium and have to wait a few years.
>
> It could probabl
On Sun, Nov 15, 2009 at 11:31 AM, "Martin v. Löwis" wrote:
>
> > Well, when I login my registered ID is www.voidspace.org.uk and *not*
> > fuzzyman.myopenid.com - so I believe you are incorrect (and in fact this
> > very point was touted as one of the advantages of openid - that your
> > account i
2009/11/15 Michael Foord :
> Well, personally I think it would be a good thing if this raised an
> exception during bytecode compilation - but it would fall under the
> moratorium and have to wait a few years.
It could probably be considered a bug, though, since the global
statement in that case s
Ezio Melotti wrote:
Python currently accepts global statements at the top level:
global foo
Beside being a meaningless operation, this might lead unexperienced
user to make mistakes like:
foo = 5
global foo # make foo global
def func():
... print foo # access the global foo
...
func()
5
Python currently accepts global statements at the top level:
global foo
Beside being a meaningless operation, this might lead unexperienced
user to make mistakes like:
foo = 5
global foo # make foo global
def func():
... print foo # access the global foo
...
func()
5
# it works!
"glob
> Well, when I login my registered ID is www.voidspace.org.uk and *not*
> fuzzyman.myopenid.com - so I believe you are incorrect (and in fact this
> very point was touted as one of the advantages of openid - that your
> account is independent of your provider and that you *can* change
> provider wh
Martin v. Löwis wrote:
So the only thing users gain with delegation is that they don't need
to remember the tedious URL that their provider assigns them. When they
switch providers, their claimed ID will still change, and they'll have
to reregister in all services they use.
No, the wh
>> So the only thing users gain with delegation is that they don't need
>> to remember the tedious URL that their provider assigns them. When they
>> switch providers, their claimed ID will still change, and they'll have
>> to reregister in all services they use.
>>
>>
> No, the whole point of d
On Sun, Nov 15, 2009 at 10:32 PM, Tarek Ziadé wrote:
>
> Ok. Fair enough, I'll work with them this way.
Although packagers should certainly fix the problems they introduce in
the first place, the second suggestion in the bug report would be
useful, independently on how linux distributions packag
Martin v. Löwis schrieb:
>> Yes, I think this just started happening. I'm guessing that the main
>> site proxies the buildbot URL requests to the buildbot master process,
>> and when it's down you get the 404s from the main server.
>>
>> I figured someone might be working on the master, though per
On Sun, Nov 15, 2009 at 4:02 AM, Terry Reedy wrote:
> Christian Heimes wrote:
>>
>> Tarek Ziadé wrote:
>>>
>>> Hello,
>>>
>>> http://bugs.python.org/issue4359 reminds me that Distutils reads build
>>> files like Makefile or pyconfig.h to get some environment
>>> variables through the sysconfig mod
Antoine Pitrou schrieb:
> Tarek Ziadé gmail.com> writes:
>>
>> This cannot work on all platforms, when our Makefile is not shipped
>> with python but python-devel. (like Fedora)
>
> This practice is stupid anyway, because it means you have to install
> python-devel even to install pure Python pa
On Sun, Nov 15, 2009 at 3:35 AM, Christian Heimes wrote:
[..]
> Do we really want to change distutils to solve a problem of a third
> party packaging system when the problem was created by the very same
> third party in the first place? In other words: Should you spend your
> precious development
Tarek Ziadé gmail.com> writes:
>
> This cannot work on all platforms, when our Makefile is not shipped
> with python but python-devel. (like Fedora)
This practice is stupid anyway, because it means you have to install
python-devel even to install pure Python packages with setuptools/distribute.
Martin v. Löwis wrote:
Fred can use his own OpenID ‘fred.example.org’, initially set up behind
the scenes to delegate to ‘bigcorp.example.com’ as the provider. Any
time he likes, Fred can *change* which provider is actually used for
authentication, without changing his OpenID. PyPI gets to find o
38 matches
Mail list logo
