Aahz wrote:
>>>Host pythondev
>>> Hostname dinsdale.python.org
>>> User pythondev
>>> IdentityFile ~/.ssh/pythondev
>>>
>>I'm confused again; are you saying that we should have a host named
>>pythondev.python.org? I'm not sure that's necessary.
>
>
> No, pythondev is simply an SSH alias for d
Barry Warsaw wrote:
> I may be totally misunderstanding, but to get shell access wouldn't I
> avoid using the pythondev account and just use my own account?
You could do that (or use the root account); I can't: I don't have
a ssh account on dinsdale. An even if I had, I couldn't write to
pythondev
On Sun, Aug 21, 2005, Barry Warsaw wrote:
> On Sun, 2005-08-21 at 09:12, "Martin v. L?wis" wrote:
>>
>> I would suggest that the default key is used for regular commits,
>> and a separate key is created for shell access. I described this
>> a bit in the PEP, essentially, in .ssh/config, I have
>>
On Sun, 2005-08-21 at 09:12, "Martin v. Löwis" wrote:
> It turns out that svn+ssh with a single account has limitations:
> you can only set the tunnel user when you are using a restricted
> key. In PEP 347, the plan is that the current SF project admins
> get shell access to the pythondev account,
Guido> The built-in namespace is searched last for a reason -- the
Guido> design is such that if you don't care for a particular built-in
Guido> you don't need to know about it.
In my mind there are three classes of builtins from the standpoint of
overriding. Pychecker complains if y
Sjoerd Mullender wrote:
> What about people with a whole host of ssh keys? I have a different key
> for each system I use (currently at least 6). Will this be supported?
> Will the different keys identify the same person?
That would be possible, yes. You should send a single file containing
all
Martin v. Löwis wrote:
> I have setup a test installation on svn.python.org, so that
> developers can see how this would work.
>
> So if you are currently a sf.net/projects/python developer,
> please send me your SSH key before August 27 or after
> September 12. We will use real names for commit m
I have setup a test installation on svn.python.org, so that
developers can see how this would work.
So if you are currently a sf.net/projects/python developer,
please send me your SSH key before August 27 or after
September 12. We will use real names for commit messages,
so if you have specific pr
Guido van Rossum wrote:
> On the hosting issue, I'm still neutral -- I expect we'll be able to
> support the current developer crowd easily on svn.python.org, but if
> we ever find ther are resource problems (either people or bandwidth
> etc.) I just received a recommendation for wush.net which spe
I made a service request at wush.net, asking for more details
about their service. There was a first response within 6 hours,
asking for more time to prepare an answer. I said I don't need
one urgently, and, with apologies, got a response one week
later.
I added the essence to the PEP; namely:
- T
It turns out that svn+ssh with a single account has limitations:
you can only set the tunnel user when you are using a restricted
key. In PEP 347, the plan is that the current SF project admins
get shell access to the pythondev account, which just has been
created.
To resolve this, project admins
Paolino wrote:
> I imagine that a method implementation of them inside the type metaclass
> could be better specified by people.
What you ask for is unimplementable. Method objects are created only
when the method is accessed, not (even) when the class is created.
Watch this:
>>> class X:
... d
I noticed (via using them) that decorations are applied to methods
before they become methods.
This choice flattens down the implementation to no differentiating
methods from functions.
1)
I have to apply euristics on the wrapped function type when I use the
function as an index key.
13 matches
Mail list logo
