Antoine Pitrou, 06.09.2013 07:43:
> Proxying wrapper? We shouldn't need that kind of tricks.
The advantage is that it's controlled by the loader, and transparent to the
module itself.
Stefan
___
Python-Dev mailing list
Python-Dev@python.org
https://ma
On Fri, 06 Sep 2013 06:50:07 +0100
Chris Withers wrote:
>
> So, from my perspective, I'm either looking at a bug in shutil.rmtree
> (which would be trying to delete a directory before deleting its content
> or failing to delete a file but ignoring an error) or the file object,
> when being use
On Mon, Sep 2, 2013 at 2:16 AM, Antoine Pitrou wrote:
> I think the biggest challenge here is to propose an API that's simple
> and easy to use (i.e. that doesn't make extension module writing more
> complicated than it currently is).
>
+1
>
> The basic concept of putting custom module objects
On Sat, Aug 31, 2013 at 1:16 PM, Stefan Behnel wrote:
> Nick Coghlan, 31.08.2013 18:49:
> > This is actually my primary motivation for trying to improve the
> > "can this be reloaded or not?" aspects of the loader API in PEP 451.
>
> I assume you mean that the extension module would be able to cl
Hi All,
Continuous testing is a wonderful thing when it comes to finding weird
edge case problems, like this one:
http://jenkins.simplistix.co.uk/job/testfixtures-tox/COMPONENTS=zc,PYTHON=3.3,label=windows/149/testReport/junit/testfixtures.tests.test_tempdirectory/TempDirectoryTests/test_check
On Sat, Aug 24, 2013 at 10:12 PM, PJ Eby wrote:
> I haven't had a chance to address this on the import-sig discussion
> yet about ModuleSpec, but I would like to just mention that one
> property of the existing module system that I'm not sure either this
> proposal or the ModuleSpec proposal pres
On Thu, 5 Sep 2013 23:26:31 -0600
Eric Snow wrote:
> On Sat, Aug 24, 2013 at 7:07 AM, Stefan Behnel wrote:
>
> > PEP 3121 would no longer be necessary. Extension types can do all we need.
> > No more special casing of modules, that was the idea.
> >
>
> One nice thing about PEP 3121 is the addi
On Sat, Aug 24, 2013 at 7:07 AM, Stefan Behnel wrote:
> PEP 3121 would no longer be necessary. Extension types can do all we need.
> No more special casing of modules, that was the idea.
>
One nice thing about PEP 3121 is the addition of md_state to module objects
to store internal module state.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/13 20:45, Eli Bendersky wrote:
> PS: I use "http://www.jcea.es/"; as my OpenID identity, and I
> delegate the actual service to "myOpenID". I can switch delegation
> trivially.
>
> http://bugs.python.org/?@action=openid_login&provider=Google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/13 22:29, Oleg Broytman wrote:
> I have seen exactly 0 (zero) sites that support Persona. Can you
> point me?
"Python España" (Python Spain) association is going to provide Persona
Only login. Deployment in four weeks.
- --
Jesús Cea Avió
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/13 23:56, Oleg Broytman wrote:
> Well, I can only use services that are available, not those that
> are promised. If python.org grows support for Persona -- who will
> be my provider and for what price? I am not going to install and
> manage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/13 22:36, Oleg Broytman wrote:
> There was no demise. Because there was no take-off. OpenID was
> never popular. I can remember a very limited set of major sites
> that allow login using OpenID: SourceForge, LiveJournal, BitBucket.
> The first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/13 21:53, Ben Finney wrote:
> My own take is that most people choose convenience and expedience
> over security and freedom, hence Facebook and Twitter and Google
> have taken over the online identity game instead of a federated
> identity sys
Barry Warsaw writes:
> On Sep 06, 2013, at 12:36 AM, Oleg Broytman wrote:
> > You cannot login using OpenID to most interesting popular sites.
> >GMail? No. Twitter? No. Facebook? FriendFeed? identi.ca? No, no, no.
>
> I'd be surprised if you ever saw the big social networking sites support
On Thu, Sep 05, 2013 at 05:29:07PM -0400, Barry Warsaw wrote:
> I don't want my choice to be log into Facebook or manage a slew of passwords.
The last part is unavoidable. I regularly login to LiveJournal,
Twitter, SourceForge, BitBucket, Gitorious, GitHub and to hundreds of
other sites -- blo
On Sep 5, 2013, at 5:56 PM, Oleg Broytman wrote:
> On Thu, Sep 05, 2013 at 05:29:07PM -0400, Barry Warsaw
> wrote:
>> I don't want my choice to be log into Facebook or manage a slew of passwords.
>
> The last part is unavoidable. I regularly login to LiveJournal,
> Twitter, SourceForge, Bit
2013/8/31 Gregory P. Smith :
> Think of the possibilities, you could even setup a test runner to
> enable/disable before and after each test, test suite or test module to
> gather narrow statistics as to what code actually _caused_ the allocations
> rather than the ultimate individual file/line doi
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
2013/9/1 Nick Coghlan :
> +1 from me for both tracemalloc and failmalloc in the same vein as
> faulthandler (and using similar API concepts to faulthandler).
>
> While I like the flat top level naming structure, we should clearly document
> these as implementation dependent runtime services. Other
On Sep 06, 2013, at 12:36 AM, Oleg Broytman wrote:
> You cannot login using OpenID to most interesting popular sites.
>GMail? No. Twitter? No. Facebook? FriendFeed? identi.ca? No, no, no.
I'd be surprised if you ever saw the big social networking sites support
OpenID or Persona. They want to o
On Sep 06, 2013, at 01:09 AM, Oleg Broytman wrote:
>I will change my mind when Google and GitHub start using them.
Neither Google nor GitHub are free or open. Bitbucket and Facebook aren't
either. I'm not saying they're bad services because of that of course, but I
don't want to have to rely on
2013/9/5 Alexander Belopolsky :
> Please mention that this API is similar to that of faulthandler and add a
> link to faulthandler docs.
Done.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
U
On Thu, Sep 05, 2013 at 04:58:19PM -0400, Tres Seaver
wrote:
> On 09/05/2013 04:29 PM, Oleg Broytman wrote:
> > I have seen exactly 0 (zero) sites that support Persona. Can you point
> > me?
>
> - From the "Mozilla Identity" blog:
>
> - - https://webmaker.org/
> - - http://bornthiswayfoundation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2013 04:33 PM, Glenn Linderman wrote:
> On 9/5/2013 1:30 PM, Tres Seaver wrote:
>> +1 for supporting Persona as an alternative to OpenID on all
>> *.python.org servers.
>
> Is there a Python implementation of Persona I can install on my web
>
There's some sample Python code here:
https://developer.mozilla.org/en-US/docs/Mozilla/Persona/Quick_Setup
The API is so simple something generic like requests suffices.
2013/9/5 Glenn Linderman :
> On 9/5/2013 1:30 PM, Tres Seaver wrote:
>
> +1 for supporting Persona as an alternative to OpenID
> Whether a given site chooses to authroize an
> authenticated-but-otherwise-unknown user to do anything meaningful is
> logically distinct.
But the least they could have done was pick a demo site that didn't do
exactly what they contend you shouldn't need to do: cough up all sorts
of personal inf
On Thu, Sep 5, 2013 at 10:33 PM, Glenn Linderman wrote:
> Is there a Python implementation of Persona I can install on my web server?
If you mean to use your web server as an Identity Provider, try this:
https://bitbucket.org/djc/persona-totp
It currently only implements TOTP-based authenticati
On Thu, Sep 5, 2013 at 10:57 PM, Donald Stufft wrote:
> Not that it changes this statement at all but you wouldn't expect to see a
> Persona login
> for gmail as persona solves the problem that people don't think of urls as
> personal
> identifiers by replacing it with emails. So Gmail would be
On Thu, 5 Sep 2013 15:40:44 -0400
Barry Warsaw wrote:
> On Sep 05, 2013, at 09:07 PM, Antoine Pitrou wrote:
>
> >Which sites exactly? I can login to BitBucket and *.python.org using
> >OpenID, not Persona.
>
> I think Persona is just too new to see it around much yet. Or maybe Mozilla
> needs
On Thu, Sep 5, 2013 at 4:29 PM, Oleg Broytman wrote:
> I have seen exactly 0 (zero) sites that support Persona. Can you
> point me?
We have an internal app that uses Persona, but we did that mostly to
play with it.
I've not run across any sites that use Persona in the wild, either.
-Fred
--
On Thu, Sep 05, 2013 at 02:07:11PM -0500, Skip Montanaro wrote:
> >> OpenID lived a short life and died a quiet death. I'm afraid Persona
> >> wouldn't live even that much. Dead-born idea, in my so humble opinion.
> >
> I was completely unaware of OpenID's demise.
There was no demise. Becaus
On Sep 5, 2013, at 4:53 PM, Barry Warsaw wrote:
> On Sep 06, 2013, at 12:36 AM, Oleg Broytman wrote:
>
>> You cannot login using OpenID to most interesting popular sites.
>> GMail? No. Twitter? No. Facebook? FriendFeed? identi.ca? No, no, no.
>
> I'd be surprised if you ever saw the big socia
On 9/5/2013 1:30 PM, Tres Seaver wrote:
+1 for supporting Persona as an alternative to OpenID on all *.python.org
servers.
Is there a Python implementation of Persona I can install on my web server?
___
Python-Dev mailing list
Python-Dev@python.org
ht
On Thu, Sep 05, 2013 at 04:53:18PM -0400, Barry Warsaw wrote:
> On Sep 06, 2013, at 12:36 AM, Oleg Broytman wrote:
> > You cannot login using OpenID to most interesting popular sites.
> >GMail? No. Twitter? No. Facebook? FriendFeed? identi.ca? No, no, no.
>
> I'd be surprised if you ever saw th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2013 04:29 PM, Oleg Broytman wrote:
> On Thu, Sep 05, 2013 at 02:50:44PM -0400, Donald Stufft
> wrote:
>> On Sep 5, 2013, at 2:43 PM, Oleg Broytman wrote:
>>> On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
>>> wrote:
Persona i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just received an email from my OpenID provider, "myOpenID", saying
that they drop OpenID service next February. I wonder what other
OpenID providers are used by other python-dev fellows.
What are you using?. bugs.python.org admins could share some d
On Thu, Sep 5, 2013 at 10:30 PM, Tres Seaver wrote:
> +1 for supporting Persona as an alternative to OpenID on all *.python.org
> servers.
BTW, I'd be happy to assist with any Persona RP implementations for
python.org services. The MDN docs are pretty good, I got my first RP
going in just a few h
On Sep 5, 2013, at 2:43 PM, Oleg Broytman wrote:
> On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
> wrote:
>> Persona is the logical successor to OpenID.
>
> OpenID lived a short life and died a quiet death. I'm afraid Persona
> wouldn't live even that much. Dead-born idea, in my s
On Thu, 05 Sep 2013 19:31:59 +0200
Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I just received an email from my OpenID provider, "myOpenID", saying
> that they drop OpenID service next February. I wonder what other
> OpenID providers are used by other python-dev fellows
On Thu, Sep 05, 2013 at 02:50:44PM -0400, Donald Stufft
wrote:
> On Sep 5, 2013, at 2:43 PM, Oleg Broytman wrote:
> > On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
> > wrote:
> >> Persona is the logical successor to OpenID.
> >
> > OpenID lived a short life and died a quiet death.
Skip Montanaro writes:
> >> On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
> >> wrote:
> >>> Persona is the logical successor to OpenID.
> >>
> >> OpenID lived a short life and died a quiet death. I'm afraid Persona
> >> wouldn't live even that much. Dead-born idea, in my so humble o
> I think Persona is just too new to see it around much yet. Or maybe Mozilla
> needs better PR.
The Persona site touts: "Signing in using Persona requires only a
valid email address; allowing you to provide personal information on
as-needed basis, when and where you think it’s appropriate."
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2013 03:52 PM, Skip Montanaro wrote:
>> I think Persona is just too new to see it around much yet. Or maybe
>> Mozilla needs better PR.
>
> The Persona site touts: "Signing in using Persona requires only a
> valid email address; allowing yo
On Sep 05, 2013, at 09:07 PM, Antoine Pitrou wrote:
>Which sites exactly? I can login to BitBucket and *.python.org using
>OpenID, not Persona.
I think Persona is just too new to see it around much yet. Or maybe Mozilla
needs better PR.
-Barry
___
Pyt
On Sep 05, 2013, at 11:33 AM, Toshio Kuratomi wrote:
>Sortof The way OAuth looks to me, it's designed to prove that a given
>client is authorized to perform an action. It's not designed to prove that
>the given client is a specific person. In some cases, you really want to
>know the latter a
>> On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
>> wrote:
>>> Persona is the logical successor to OpenID.
>>
>> OpenID lived a short life and died a quiet death. I'm afraid Persona
>> wouldn't live even that much. Dead-born idea, in my so humble opinion.
>
> I don't think there's muc
On Thu, 5 Sep 2013 14:50:44 -0400
Donald Stufft wrote:
>
> On Sep 5, 2013, at 2:43 PM, Oleg Broytman wrote:
>
> > On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
> > wrote:
> >> Persona is the logical successor to OpenID.
> >
> > OpenID lived a short life and died a quiet death. I'
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, 05 Sep 2013 19:31:59 +0200
Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I just received an email from my OpenID provider, "myOpenID", saying
> that they drop OpenID service next February. I wonder what other
> OpenID providers are used by other python-dev fellows
On Thu, Sep 05, 2013 at 02:35:16PM -0400, Donald Stufft
wrote:
> Persona is the logical successor to OpenID.
OpenID lived a short life and died a quiet death. I'm afraid Persona
wouldn't live even that much. Dead-born idea, in my so humble opinion.
Oleg.
--
Oleg Broytmanhtt
On Thu, Sep 5, 2013 at 10:31 AM, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I just received an email from my OpenID provider, "myOpenID", saying
> that they drop OpenID service next February. I wonder what other
> OpenID providers are used by other python-dev fellows.
On Sep 5, 2013, at 2:25 PM, 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 OpenID -- there are too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sep 05, 2013, at 07:31 PM, Jesus Cea wrote:
>I just received an email from my OpenID provider, "myOpenID", saying
>that they drop OpenID service next February. I wonder what other
>OpenID providers are used by other python-dev fellows.
>
>What ar
On Thu, Sep 05, 2013 at 07:31:59PM +0200, Jesus Cea wrote:
> I just received an email from my OpenID provider, "myOpenID", saying
> that they drop OpenID service next February. I wonder what other
> OpenID providers are used by other python-dev fellows.
>
> What are you using?. bugs.python.org ad
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 OpenID -- there are too few sites that allow
> > full-featured login with OpenID
On Sep 5, 2013, at 2:12 PM, Oleg Broytman wrote:
> On Thu, Sep 05, 2013 at 07:31:59PM +0200, Jesus Cea wrote:
>> I just received an email from my OpenID provider, "myOpenID", saying
>> that they drop OpenID service next February. I wonder what other
>> OpenID providers are used by other python-
56 matches
Mail list logo
