jessenoller.com comments - Latest Comments

Re: SSH Programming with Paramiko | Completely Different

jnoller — Fri, 13 Nov 2009 06:18:05 -0000

You should email the paramiko mailing list for support

Re: SSH Programming with Paramiko | Completely Different

hima — Fri, 13 Nov 2009 05:08:51 -0000

sudo over paramiko doesn't work. It gives exception that " U require a tty to run sudo".
My server is having requiretty = true . Due to security problem, this setting cant be changed. I will have to handle it through paramiko.
Pls Help........

Re: PyPI Poll: Comments and Ratings

Ludvig Ericson — Fri, 13 Nov 2009 05:00:40 -0000

Right on.

Suffice to say, there was some suppressed tension on the subject on python-dev. I blurted out my frustration with PyPI, and it exploded.

Re: PyPI Poll: Comments and Ratings

elpargo — Fri, 13 Nov 2009 00:48:15 -0000

So basically you are saying the poll itself is broken.

Re: PyPI Poll: Comments and Ratings

jnoller — Thu, 12 Nov 2009 23:23:14 -0000

You're really no fun.

Re: PyPI Poll: Comments and Ratings

jackdied — Thu, 12 Nov 2009 23:20:27 -0000

I checked my mail and a py-dev thread that was only hours long had 90 messages. I ran away.

Re: PEP 3003: “Python Language Moratorium” – Accepted

jnoller — Mon, 09 Nov 2009 20:27:25 -0000

It was brought up in the discussions of this pep on python-dev, I
don't remember ther arguments against it, but there were a few.

Re: PEP 3003: “Python Language Moratorium” – Accepted

twitter-18206057 — Mon, 09 Nov 2009 20:22:35 -0000

EDIT: woops, left a duplicate because I thought the first comment got deleted.

Re: PEP 3003: “Python Language Moratorium” – Accepted

Brendan Miller — Mon, 09 Nov 2009 20:15:11 -0000

Has anyone talked about putting together some kind of formal standard for Python? It seems like the number of implementations has been growing steadily, and core language features are solidifying, so this seems like an appropriate time.

Probably a subset of python 3 that doesn't include the entire CPython standard library, and doesn't specify features that would be difficult to implement in some environments, like the JVM. That would provide a non-moving minimal target both for implementers, and for people wanting to write portable code.

Re: PyCon 2010: Talks are live!

Jospeh Lisee — Thu, 05 Nov 2009 00:51:20 -0000

Thanks for going through effort organizing PyCon!

Re: SSH Programming with Paramiko | Completely Different

jnoller — Fri, 30 Oct 2009 17:48:55 -0000

Given the article was about SSH programming, and paramiko is for SSH
programming - I think it's a much better fundamental solution to SSH
programming than pexpect. I've had plenty of expect-like scripts, and
expect-base script break because assumption on output, regexes, etc
broke. I agree that paramiko isn't a generalized tool, but for the
problem it tries to solve it is the best tool (in my opinion).

If we were talking a general "watch something and react" tool, then
yeah - pexpect makes sense, but we're not.

Re: SSH Programming with Paramiko | Completely Different

mikepenn — Fri, 30 Oct 2009 17:35:54 -0000

Actually something expect-like doesn't care what the output is if you code the same way you do with paramiko. pexpect.expect takes a list of args... that list can be regular expressions or perhaps pexpect.TIMEOUT or pexpect.EOF. Based on that which one in that list matches, you make a decision; this is not an issue of a small decision tree. I'm ok with people using other tools, but lets be fair to the tools available. pexpect is a much more generalized solution than paramiko; paramiko gives you more granular visibility into stderr than pexpect does, but paramiko is limited to ssh.

Re: SSH Programming with Paramiko | Completely Different

jnoller — Fri, 30 Oct 2009 14:36:31 -0000

Personally, I've found any tool which waits for specific output from
commands to be terribly brittle. Output from remote sources can (and
does) frequently change - sure, something expect-like does the job if
you can count on the same output over and over again.

I know pexpect has gotten better since the time I used it, which
admittedly was awhile ago and at this point I go out of my way to
avoid it/expect-like tools unless I simply can't. I'm also much more a
fan of tackling things with tools like paramiko, which is more
programmatic/reliable in my mind.

Re: Dive Into Python 3: The Foreward

jnoller — Tue, 27 Oct 2009 23:00:56 -0000

Any text in the foreword is under the same license as the book itself! Go for it!

Re: Dive Into Python 3: The Foreward

Giulio Piancastelli — Tue, 27 Oct 2009 13:31:31 -0000

I have translated Dive Into Python 3 in Italian and I would like both to translate also your foreword and to put it alongside the book's translated text. First question: am I allowed to do it? Both the original and the translated book's text are licensed under CC-BY-SA 3.0. So, second question: have you attached / do you want to attach a specific content license to the foreword text as published on this page? (Possibly, a license that would allow me to translate it and publish it on similar terms?) Thanks!

Re: SSH Programming with Paramiko | Completely Different

mikepenn — Tue, 27 Oct 2009 11:47:05 -0000

I'm curious about something mentioned above... you seem to discourage use of pexpect for driving ssh sessions, but you launched into issues with 'subprocess' without specific comments about why pexpect isn't a winner for you. Have you had bad experiences with pexpect, and if so please elaborate...

Having used pexpect to drive cisco routers for the last 3 years, I have to say it's been nothing but pleasant to me.

Thoughts?
\m

Re: Dive Into Python 3: The Foreward

jnoller — Mon, 26 Oct 2009 21:10:58 -0000

Thank you; again

Re: Dive Into Python 3: The Foreward

Thijs — Mon, 26 Oct 2009 21:02:10 -0000

There's another 'foreward' typo in the first sentence of this blogpost..

Re: Dive Into Python 3: The Foreward

jnoller — Mon, 26 Oct 2009 09:06:43 -0000

Why are you bustin my balls? ;)

Actually, juggling work-work with open-source work and being a parent is a painful process for me, honestly. It doesn't help I'm a severe workaholic. I'd be perfectly fine with 12 hour workdays :|

Re: Dive Into Python 3: The Foreward

twitter-7645442 — Mon, 26 Oct 2009 08:35:46 -0000

Jesse,

Great foreword, but just one little thing:

If you're coding *between* your daughter's naps (e.g., when she's awake), what are you doing *during* her naps (when she's asleep)? And when do you find time to spend with her?

;-P

Congrats on the honor, and my experience "diving into" python mirrors yours.
brian

Re: Dive Into Python 3: The Foreward

jnoller — Mon, 26 Oct 2009 07:48:59 -0000

I already read Guido's proposal - I volunteered to draft the PEP (it's in progress) for the moratorium. I know that the 2/3 split will mark a pause - I'm for pausing. Being in core dev, my boogeyman has been the standard library - I'd like to see more focus on that, improving, cleaning, testing and other areas outside of the syntax and builtins.

It will be interesting ;)

Re: Dive Into Python 3: The Foreward

jnoller — Mon, 26 Oct 2009 07:46:22 -0000

Argh. Fixed.

Re: Dive Into Python 3: The Foreward

tag — Mon, 26 Oct 2009 05:09:49 -0000

Great intro, Jesse. It comes at a time when I'm reassessing Python 3 (nearly a year since the first official release) and what it means for the language. I hope to post these thoughts on my own blog soon. In the meantime:

Python 3 also doesn’t end the evolution of the language – not by any stretch. New features, syntax and libraries are still being added, and will probably be added, tweaked and removed for as long as Python itself lives on.

You will have read Guido van Rossum's recent proposal which recommends a moratorium on changes to Python syntax. He also says:

The main goal of the Python development community at this point should be to get widespread acceptance of Python 3000.

Reading between the lines, I think the Python 2/3 fork will mark a significant pause in the evolution of the language. The overhead of developing, supporting and maintaining two versions of everything is high. New features would have to be backported. Libraries need to work on two platforms. Alternative implementations have two targets. Etc.

I'm interested to see how things pan out. Certainly, it's refereshing to read a book like Mark Pilgrim's, which really does dive right in.

Re: Dive Into Python 3: The Foreward

technomalogical — Mon, 26 Oct 2009 00:25:52 -0000

Also, did he really ask if you'd be "interesting"? :)

Re: Dive Into Python 3: The Foreward

jnoller — Sun, 25 Oct 2009 14:35:07 -0000

Typo, thanks for catching it - fixed