Hi Brett,
On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:
> I also plan to rewrite the import machinery in pure Python.
http://codespeak.net/svn/pypy/dist/pypy/module/__builtin__/importing.py
A bientot,
Armin
___
Python-Dev mailing list
Jason Orendorff wrote:
> On 7/21/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>> However, I'm also struggling to think of a case other than list vs deque
>> where
>> the choice of a builtin or standard library data structure would be dictated
>> by big-O() concerns.
>
> OK, but that doesn't mean t
Grig Gheorghiu wrote:
> Please let me know if you're interested.
As I said earlier: If you need some kind of post-commit
trigger on the python repository to trigger a build, just
let me know. We currently use a more-or-less plain
svn_buildbot.py to trigger our own builds.
Regards,
Martin
Hi,
On Sat, Jul 22, 2006 at 12:33:45PM +1000, Nick Coghlan wrote:
> Agreed, but there's more to doing that than just writing down the O() implied
> by the current CPython implementation - it's up to Guido to decide which of
> the constraints are part of the language definition, and which are
>
Re-hi,
On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:
> http://svn.python.org/view/python/branches/bcannon-sandboxing/securing_python.txt?rev=50717&view=log.
I'm not sure I understand what you propose to fix holes like
constructors and __subclasses__: it seems that you want to remo
On 7/22/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Grig Gheorghiu wrote:> Please let me know if you're interested.As I said earlier: If you need some kind of post-committrigger on the python repository to trigger a build, justlet me know. We currently use a more-or-less plain
svn_buildbot.py
Grig Gheorghiu wrote:
> As I said earlier: If you need some kind of post-commit
> trigger on the python repository to trigger a build, just
> let me know. We currently use a more-or-less plain
> svn_buildbot.py to trigger our own builds.
>
> Wouldn't that put too much of a burden o
On 7/22/06, Armin Rigo <[EMAIL PROTECTED]> wrote:> Re-hi,> > On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:> >
http://svn.python.org/view/python/branches/bcannon-sandboxing/securing_python.txt?rev=50717&view=log.> > I'm not sure I understand what you propose to fix holes like> const
On 7/22/06, Armin Rigo <[EMAIL PROTECTED]> wrote:
Hi Brett,On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:> I also plan to rewrite the import machinery in pure Python.
http://codespeak.net/svn/pypy/dist/pypy/module/__builtin__/importing.pyThanks for the link, Armin. Since you guys do
On 7/22/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Grig Gheorghiu wrote:> As I said earlier: If you need some kind of post-commit> trigger on the python repository to trigger a build, just> let me know. We currently use a more-or-less plain
> svn_buildbot.py to trigger our own
Armin Rigo wrote:
> I'm not sure I understand what you propose to fix holes like
> constructors and __subclasses__: it seems that you want to remove them
> altogether (and e.g. make factory functions instead). That would
> completely break all programs, right? I mean, there is no way such
> chan
Armin Rigo wrote:
> Re-hi,
>
> On Wed, Jul 19, 2006 at 03:35:45PM -0700, Brett Cannon wrote:
>
>>http://svn.python.org/view/python/branches/bcannon-sandboxing/securing_python.txt?rev=50717&view=log.
>
> I'm not sure I understand what you propose to fix holes like
> constructors and __subclasses_
Hi Brett,
On Sat, Jul 22, 2006 at 10:33:19AM -0700, Brett Cannon wrote:
> Thanks for the link, Armin. Since you guys don't have the import
> restrictions the CPython version would have and just have different coding
> needs for RPython obviously I can't just do a blind copy. But I will
> definit
13 matches
Mail list logo
