John Ladasky <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]
com:
> Hi folks,
>
> Running Python 2.5 on both a Windows XP laptop, and an Ubuntu
> Linux 7.04 desktop.
>
> I've gotten tired of maintaining multiple copies of my personal
> modules that I use over and over. I have copies of the
"John Ladasky" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| On Windows I found a solution that works, but which may be a kludge.
| In the Python "site-packages" folder, I added a sub-folder called "my-
| packages". Then I created a text file, "my-packages.pth", containing
| the
On Tue, 03 Jun 2008 17:57:07 -0700, John Ladasky wrote:
> Hi folks,
>
> Running Python 2.5 on both a Windows XP laptop, and an Ubuntu Linux
> 7.04 desktop.
>
> I've gotten tired of maintaining multiple copies of my personal
> modules that I use over and over. I have copies of these files in the
On Jun 3, 6:52 pm, Ben Finney <[EMAIL PROTECTED]>
wrote:
> John Ladasky <[EMAIL PROTECTED]> writes:
> > I want to know what is the *recommended* way to integrate my own
> > personal modules with Python. Thanks!
>
> You want the 'distutils' documentation
> http://www.python.org/doc/lib/module-distu
John Ladasky <[EMAIL PROTECTED]> writes:
> I want to know what is the *recommended* way to integrate my own
> personal modules with Python. Thanks!
You want the 'distutils' documentation
http://www.python.org/doc/lib/module-distutils> and the documents
that it references, which will lead you to
Hi folks,
Running Python 2.5 on both a Windows XP laptop, and an Ubuntu Linux
7.04 desktop.
I've gotten tired of maintaining multiple copies of my personal
modules that I use over and over. I have copies of these files in the
same directory as the main program I happen to be working on at the
ti
Duncan Booth wrote:
[CUT]
>
> C:\>cd /Documents and settings
> The system cannot find the path specified.
>
> C:\>cd /DDocuments and settings
>
> C:\Documents and Settings>
that's because the
cd /D is interpreted as
"change drive and directory"
so I imagine it enables some kind of command extensi
Andy Dingley wrote:
>> Python and Ubuntu rock...go fot it.
>
> That's nice. I've just burned myself a new Ubuntu f*ck-a-duck release CD
Now, just out of curiosity, what's f*ck-a-duck?
Baalbek
--
http://mail.python.org/mailman/listinfo/python-list
Duncan Booth wrote:
> Bryan Olson wrote:
>
>> Duncan Booth wrote:
>>> Any other Microsoft commands I try all complain about 'invalid
>>> switch'.
>>
>> The first I noticed were their build tools. Their version of
>> "make", called "nmake", and their visual studio tools will
>> accept either forw
On Tue, 1 Aug 2006 14:47:59 -0300, Gerhard Fiedler <[EMAIL PROTECTED]> wrote:
> On 2006-08-01 12:31:01, Sybren Stuvel wrote:
...
> Is that really true? From what I know, it's more like this:
>
> - Unix-type systems: '/'
> - Windows-type systems: '\'
> - Mac OS: ':'
> - OpenVMS: '.'
> - ...
>
> Mayb
On 2006-08-04 09:58:34, Sybren Stuvel wrote:
>> They all (well, most of them) use computers in their administration;
>> /that's/ the cost I was talking about, not the cost for the software
>> industry :)
>
> Good point. Time more people started using Open Source :)
Definitely. But don't hold you
On Fri, Aug 04, 2006 at 02:01:58PM +0200, Sybren Stuvel wrote:
> > OS/2 (and eComStation) also uses the backslash as the path
> > separator.
>
> You mean OS/2 is still in actual use?
'fraid so. :-)
--
http://mail.python.org/mailman/listinfo/python-list
On 2006-08-04 05:30:00, Sybren Stuvel wrote:
>> Besides, you probably don't know whether it's not one of your direct
>> suppliers who's affected. You're sure you don't buy from anybody
>> running a Windows system? I'd bet against that, and I only bet when
>> I know I win :)
>
> Good point. I don'
Bryan Olson wrote:
> Duncan Booth wrote:
>> I'm not sure ambiguity enters into it. I think perhaps the bad
>> detection of the option happens because the CD command can ignore
>> spaces in its argument. Since it is ignoring spaces they don't
>> actually require a space after the option strings.
>
On Tue, Aug 01, 2006 at 05:31:01PM +0200, Sybren Stuvel wrote:
> James Stroud enlightened us with:
> > its better to use:
> >
> >os.path.join('my', 'favorite', 'dir')
> >
> > than
> >
> >"\\".join(['my', 'favorite', 'dir'])
> >
> > because the latter will bonk on linux.
>
> Ehm... replace
Duncan Booth wrote:
> Bryan Olson wrote:
>
>> Not quite. The first slash is ambiguous and apparently ignored,
>> but latter slashes are taken as a path separators.
>
> I'm not sure ambiguity enters into it. I think perhaps the bad detection of
> the option happens because the CD command can igno
Bryan Olson wrote:
> Not quite. The first slash is ambiguous and apparently ignored,
> but latter slashes are taken as a path separators.
I'm not sure ambiguity enters into it. I think perhaps the bad detection of
the option happens because the CD command can ignore spaces in its
argument. Sinc
Duncan Booth wrote:
> Bryan Olson wrote:
>
>> Duncan Booth wrote:
>>> [EMAIL PROTECTED] wrote:
>>>
>From a WinXP command prompt:
C:\>
C:\>cd /windows/system32
C:\WINDOWS\system32>
>>> Not from my Windows XP command prompt it doesn't. Do you have
Bryan Olson wrote:
> Duncan Booth wrote:
>> [EMAIL PROTECTED] wrote:
>>
>>> >From a WinXP command prompt:
>>>
>>> C:\>
>>> C:\>cd /windows/system32
>>>
>>> C:\WINDOWS\system32>
>>>
>>>
>> Not from my Windows XP command prompt it doesn't. Do you have anything
>> strange installed on y
On 2006-08-03 04:53:11, Sybren Stuvel wrote:
>> Pretty much every production cost increase gets in the end paid by
>> the consumer. With some localized changes, you may be lucky and
>> don't buy any products that are affected, but with such a widespread
>> change as this would be, it is more like
Christopher Weimann wrote:
> On 08/02/2006-08:06AM, [EMAIL PROTECTED] wrote:
>> From a WinXP command prompt:
>>
>> C:\>
>> C:\>cd /windows/system32
>>
>> C:\WINDOWS\system32>
>>
>>
>
>
> This doesn't work the way you think it does.
>
> C:\>cd /windows
>
> C:\WINDOWS>cd /system32
>
Duncan Booth wrote:
> [EMAIL PROTECTED] wrote:
>
>> >From a WinXP command prompt:
>>
>> C:\>
>> C:\>cd /windows/system32
>>
>> C:\WINDOWS\system32>
>>
>>
> Not from my Windows XP command prompt it doesn't. Do you have anything
> strange installed on your system?
Tons of strange stuff
Sybren Stuvel <[EMAIL PROTECTED]> wrote:
> Gerhard Fiedler enlightened us with:
> > I don't know how many reasons you need besides backward
> > compatibility, but all the DOS (still around!) and Windows apps that
> > would break... ?!? I think breaking that compatibility would be
> > more expensi
On 2006-08-02 21:09:43, Sybren Stuvel wrote:
> Microsoft could provide an emulated environment for backward
> compatability, just like Apple did. Wouldn't know what that would cost,
> though.
Possibly. Rather than waiting for that, I think that languages that want a
degree of portability should s
Gerhard Fiedler <[EMAIL PROTECTED]> wrote:
...
> > Part of the CP/M compatibility did include the use of / as flag-indicator
> > (the use of \r+\n as line ending also comes from CP/M -- in turn, CP/M
> > had aped these traits from some DEC minicomputer operating systems).
>
> At the time, proba
On 2006-08-02 17:36:06, Sybren Stuvel wrote:
> IMO it's too bad that "they" chose \r\n as the standard. Having two
> bytes as the end of line marker makes sense on typewriters and
> similarly operating printing equipment.
I may well be mistaken, but I think at the time they set that standard,
s
On 08/02/2006-08:06AM, [EMAIL PROTECTED] wrote:
>
> >From a WinXP command prompt:
>
> C:\>
> C:\>cd /windows/system32
>
> C:\WINDOWS\system32>
>
>
This doesn't work the way you think it does.
C:\>cd /windows
C:\WINDOWS>cd /system32
C:\WINDOWS\system32>
C:\WINDOWS\system32>cd
On 2006-08-02 17:38:54, Sybren Stuvel wrote:
> Gerhard Fiedler enlightened us with:
>>> Microsoft did *NOT* write DOS
>>
>> Well, they didn't write most of DOS 1.0. But it seems they did write
>> (or at least specify) most if not all of the rest up to DOS 6.22 or
>> so. Which is possibly consider
Tim Chase wrote:
> Nice to see consistancy at work. Looks like leading slashes are
> stripped and so it trys to find it relative to the current path.
>
> Nothing like predictable, cross-platform implementations there.
> [rolls eyes]
>
> Thank goodness Python brings some brains to the table wh
On 2006-08-02 12:41:44, Alex Martelli wrote:
> Microsoft did *NOT* write DOS
Well, they didn't write most of DOS 1.0. But it seems they did write (or at
least specify) most if not all of the rest up to DOS 6.22 or so. Which is
possibly considerable.
> Part of the CP/M compatibility did include
On 2006-08-02 13:24:10, Dennis Lee Bieber wrote:
> Change Directory may work... but
>
> C:\Documents and Settings\Dennis Lee Bieber>cd c:\
>
> C:\>cd /windows/system32
>
> C:\WINDOWS\SYSTEM32>cd c:\
>
> C:\>dir /windows/system32
> Parameter format not correct - "windows".
Since '/' is u
On 2006-08-02 11:29:18, Sybren Stuvel wrote:
> John Salerno enlightened us with:
>> But of course I still agree with you that in either case it's not a
>> judgment you can fairly make 30 years after the fact.
>
> I don't see Microsoft changing it the next 30 years either... Apple
> moved from \r
Sybren Stuvel wrote:
> Apple
> moved from \r to \n as EOL character.
Interesting. I didn't know that. Although it does seem to make sense to
use both \r\n as EOL (if you still consider one as a carriage return and
one as a newline, a la old school typewriters), \n is much nicer and
cleaner loo
> | Not from my Windows XP command prompt it doesn't. Do you have
> | anything
> | strange installed on your system?
>
> FWIW:
>
>
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> c:\temp>cd \
>
> C:\>cd /windows/System32
>
> C:\windows\system32>
>
jean-michel bain-cornu <[EMAIL PROTECTED]> wrote:
> Andy Dingley a écrit :
> > I'd never recommend dual-boot for anything!
> Don't agree man, it's good for testing...
It's bothersome for testing: virtualization is much handier in most
cases.
Alex
--
http://mail.python.org/mailman/listinfo/pyth
Gerhard Fiedler <[EMAIL PROTECTED]> wrote:
...
a few fine points of computing history...:
> >> (URLs probably use the slash because the internet protocols have been
> >> developed largely on Unix-type systems for use with Unix-type systems?)
> >
> > It wasn't designed specifically for Unix-ty
| [EMAIL PROTECTED] wrote:
|
| >>From a WinXP command prompt:
| >
| > C:\>
| > C:\>cd /windows/system32
| >
| > C:\WINDOWS\system32>
| >
| >
| Not from my Windows XP command prompt it doesn't. Do you have
| anything
| strange installed on your system?
FWIW:
Microsoft Windows
[EMAIL PROTECTED] wrote:
>>From a WinXP command prompt:
>
> C:\>
> C:\>cd /windows/system32
>
> C:\WINDOWS\system32>
>
>
Not from my Windows XP command prompt it doesn't. Do you have anything
strange installed on your system?
--
http://mail.python.org/mailman/listinfo/python-list
ved from \r to \n as EOL character. I'm sure the folks at mickeysoft
> are smart enough to change from \ to /.
They dis-allow '/' in filenames, and many Microsoft products now
respect
'/' as an alternate to '\'.
>From a WinXP command prompt:
C:\&
"Gerhard Fiedler" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>With the same reasoning one could say that the Unix creators should have
> used the VMS (or any other existing) form.
Only if they used Guido's time machine.
--
http://mail.python.org/mailman/listinfo/python-list
Gerhard Fiedler wrote:
> A design choice is not necessarily a
> bad choice just because it turns out that some 30 years later there is a
> similar common product whose creators made a different choice, and now
> programmers have to cater to both.
To be fair, this isn't the reason he gave for it b
On 2006-08-02 04:42:31, Sybren Stuvel wrote:
> I never said "I would have known it better". I just said that IMO it
> was a bad design choice ;-)
Well, and I question your qualification to judge that.
In order to say that, you would have to know the reasoning, would have to
put it in the histor
Edmond Dantes wrote:
> Dan wrote:
>
>> But taken out of that context, I'll challenge it. I was first exposed
>> to Python about five or six years ago--my boss asked me to consider it.
>> What I found was that the current version of Python was V2.2, but newest
>> version (that I could find) that r
On 2006-08-01 16:29:54, Sybren Stuvel wrote:
>> - Mac OS: ':'
>
> It's a slash too, at least on non-obsolete Mac OS versions.
I wrote "Mac OS". That's not "Mac OSX". Ask Apple... :) And Mac OSX is
quite arguably a Unix-type system.
>> Maybe someone else can fill in some of the missing OSes. It
On 2006-08-01 12:31:01, Sybren Stuvel wrote:
> Ehm... replace that with "the latter with bonk on every OS except
> Microsoft Windows". Windows is the weird one in OS-land, because they
> are the only one that use the most widely used escape-character (the
> backslash) as path separator.
Is that r
Dan wrote:
> But taken out of that context, I'll challenge it. I was first exposed
> to Python about five or six years ago--my boss asked me to consider it.
> What I found was that the current version of Python was V2.2, but newest
> version (that I could find) that ran on VMS was V1.4. I decide
That is important, but apparently Windows (at least XP) will work fine
with the forward slash that Linux uses. I just tried it in the command
prompt and it works. I'm sure other platforms use the forward slash
separator as well. You've just covered three major platforms (Mac OS X,
WinXP and Linux)
[EMAIL PROTECTED] wrote:
> Python and Ubuntu rock...go fot it.
That's nice. I've just burned myself a new Ubuntu f*ck-a-duck release
CD intending to rebuild a flakey old Deadrat box with it. Once it's
done I'd like to be running Python with some USB to Dallas one-wire
hardware on it, re-plugged
Andy Dingley wrote:
[snip]
> Python is one of the best languages I've found for
> platform-independence - significantly better than Perl.
[big snip]
This statement was given in the context of Windows and Linux, and I've
precious little experience doing anything on Windows. So I won't
challenge
> I'd never recommend dual-boot for anything!
> Hardware is cheap, time and trouble is expensive.
Dual-booting if so easy and helpful, I have always found it to be
extremely useful.
You might have a bad experience but I have my laptop and desktop both
running dual boot successfully for 4 and a ha
Linux can let you do more in Python and this comes from my personal
exprience. Ubuntu Dapper should let you install drivers easily for
wireless...a little bit tweaking might be required but its worth the
effort. Python and Ubuntu rock...go fot it.
[EMAIL PROTECTED] wrote:
> Okay, once-upon-a-time
jean-michel bain-cornu wrote:
>Take care to use os.sep
This is an important point. You should read up on the os.path module to
make sure you are doing things in a platform independent way, for
example, its better to use:
os.path.join('my', 'favorite', 'dir')
than
"\\".join(['my', 'favor
metaperl wrote:
> The reason I'm going with vmware is because I'm afraid that I will need
> to compile a C portiion of a Python module and that will not be a
> pretty picture under Windows... true or false?
>
Provided you have the correct compilers installed it is no harder compiling
C extensions
On Mon, Jul 31, 2006 at 04:30:50AM -0700, Andy Dingley wrote:
>[EMAIL PROTECTED] wrote:
>
>> Is Windows
>> an okay enviornment in which to program under Python, or do you
>> recommend that I run a dual-boot of Linux or maybe a VMWare install
>> to
>> program under Python?
>
>Python is one of the be
Andy Dingley wrote:
>
> Python is one of the best languages I've found for
> platform-independence - significantly better than Perl.
The reason I'm going with vmware is because I'm afraid that I will need
to compile a C portiion of a Python module and that will not be a
pretty picture under Wind
Andy Dingley a écrit :
> I'd never recommend dual-boot for anything!
Don't agree man, it's good for testing...
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
> Is Windows
> an okay enviornment in which to program under Python, or do you
> recommend that I run a dual-boot of Linux or maybe a VMWare install to
> program under Python?
Python is one of the best languages I've found for
platform-independence - significantly better
Hi,
[EMAIL PROTECTED] a écrit :
> Is Windows
> an okay enviornment in which to program under Python, or do you
> recommend that I run a dual-boot of Linux or maybe a VMWare install to
> program under Python?
I'm used to practice windows & linux and it makes sense to use python on
both because the
I am not a programming expert but I use python everyday on Windows XP:
* python standard distribution (CPython)
* iPython
* cygwin for the command line interaction, add a unix/linux flavour to
the blend
EuGeNe
--
http://mail.python.org/mailman/listinfo/python-list
Windows XP is fine. I am learning Python on Windows first with an eye
toward moving to Linux.
If you like, get the ActivePython distribution, which comes with the
Win32 extensions.
If you start liking Python, consider adding the IPython shell. There
are commandline tweaks you can do to make the X
[EMAIL PROTECTED] wrote:
> Okay, once-upon-a-time I tried to start programming by learning C. At
> the time I was younger and didn't really understand all that C had to
> offer. I eventually moved over to Microsoft's Visual Basic. It was
> nice to be able to design a visual application with no e
Python should port nicely between Windows and Linux so there should be
no need to dual-boot.
[EMAIL PROTECTED] wrote:
> Okay, once-upon-a-time I tried to start programming by learning C. At
> the time I was younger and didn't really understand all that C had to
> offer. I eventually moved over t
On Sun, Jul 30, 2006 at 04:21:34PM -0700, [EMAIL PROTECTED] wrote:
>offer. I eventually moved over to Microsoft's Visual Basic. It was
I'm very sorry.
>Long story short, I want to get back into programming, and Python looks
>like a good choice for me to start with, and maybe become advanced
>
> Right now I run Windows as my main operating system. On my old
> laptop I ran Ubuntu, and liked it very much; however, my new laptop has
> a Broadcom wireless card, and it's not very Linux friendly.
of topic: that Broadcom wireless card has a driver included in the latest
kernel 2.6.17, and pro
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
>
>Long story short, I want to get back into programming, and Python looks
>like a good choice for me to start with, and maybe become advanced
>with. Right now I run Windows as my main operating system. On my old
>laptop I ran Ubuntu, an
Okay, once-upon-a-time I tried to start programming by learning C. At
the time I was younger and didn't really understand all that C had to
offer. I eventually moved over to Microsoft's Visual Basic. It was
nice to be able to design a visual application with no effort (too bad
I didn't really le
On 2005-10-26, Tim Golden wrote:
> [Sybren Stuvel]
>
> Tim Golden enlightened us with:
>> > Well, I'm with you. I'm sure a lot of people will chime in to point
>> > out just how flexible and useful and productive Linux is as a
>> > workstation, but every time I try to use it -- and I make an honest
Tim G enlightened us with:
> Sadly, this seems not to be the case on my Ubuntu Breezy: bash
> 3.00.16, libreadline 4.3/5.0 (not sure which one bash is using).
> ctrl-r is fine; but you can't down-arrow from there; it just beeps
> at you. Is there some setting I'm missing?
See my other post in this
On Wednesday 26 October 2005 07:20, Tim Golden wrote:
> I'm sure you're right: given moderately naive users, a Windows box
> is *extremely* likely to be zombified. It's just that it doesn't
> have to be that way with the proper care and attention.
With $200 dollars of antivirus software (on top of
Bernhard Herzog wrote:
> "Tim Golden" <[EMAIL PROTECTED]> writes:
>
> > But as far as I can tell
> > from my experience and from the docs -- and I'm not near a
> > Linux box at the mo -- having used ctrl-r to recall line x
> > in the history, you can't just down-arrow to recall x+1, x+2 etc.
> > O
Tim Golden enlightened us with:
> Well, fair enough. Although I don't think that on its own this
> constitutes "rubbish".
True - it's just one of the reasons that shift its status toward
rubishness ;-)
> Not quite sure what this means. As in ANSI support? (Perfectly true
> - definitely lacking th
Thomas Heller wrote:
> FYI, if you don't know this already: You also can resize the console without
> going through the properties menu with 'mode con cols=... lines=...'.
Good grief! I haven't used "mode con" in years; forgotten
it even existed! Thanks for bringing that back, Thomas.
TJG
--
ht
> Thanks to both of you. But that much I already knew. It's not
> that I have *no* knowledge about readline: I did at least
> read the manuals when I got stuck! But as far as I can tell
> from my experience and from the docs -- and I'm not near a
> Linux box at the mo -- having used ctrl-r to reca
Tim> I am quite well aware of all of the ways you mention of recalling
Tim> history etc. etc. When I've tried using them, they all seem
Tim> tiresomely cumbersome ...
That's not at all surprising (at least not to me). An important point to
realize is that readline's command recall is
[Giovanni Dall'Olio]
Tim Golden ha scritto:
[... bash vs Win command-line ...]
> Argh!! ;)
> How about reading a simple tutorial on bash?
[... snip signs of aggravation over my ignorance ...]
I am quite well aware of all of the ways you mention
of recalling history etc. etc. When I've tried usi
"Tim Golden" <[EMAIL PROTECTED]> writes:
> [Sybren Stuvel]
>> You can't resize it horizontally
>
> Well, peculiarly, you can do this (as you're probably aware) from
> the Properties menu and it'll work immediately, albeit without
> advising the running programs that it's resized, so only new
> li
[Tim Golden]
> Just occasionally you read posts from people who say (synthesised)
> "The Windows command line is rubbish",
[Sybren Stuvel]
> It is. Let me give an example. I have the following files:
[.. snip example of finding .somefile when you type som ..]
Well, fair enough. Although I don't
Tim Golden enlightened us with:
> Well yes. I think the (only slightly) wider point I was making was
> that -- despite goodwill and several attempts on my part -- Linux
> still has not overpowered me with its usefulness.
I have yet to see any OS that overpowers me with its usefulness.
> Extending
Tim Golden ha scritto:
> As it happens, (and I suspect I'll have to don my flameproof suit here),
> I prefer the Windows command line to bash/readline for day-to-day use,
> including in Python. Why? Because it does what I can't for the life of
> me get readline to do: you can type the first few
Tim Golden enlightened us with:
> But as far as I can tell from my experience and from the docs -- and
> I'm not near a Linux box at the mo -- having used ctrl-r to recall
> line x in the history, you can't just down-arrow to recall x+1, x+2
> etc. Or can you?
[Sybren]
With bash as well as the Py
"Tim Golden" <[EMAIL PROTECTED]> writes:
> But as far as I can tell
> from my experience and from the docs -- and I'm not near a
> Linux box at the mo -- having used ctrl-r to recall line x
> in the history, you can't just down-arrow to recall x+1, x+2 etc.
> Or can you?
[Bernhard Herzog]
> Yo
Tim Golden enlightened us with:
> But as far as I can tell from my experience and from the docs -- and
> I'm not near a Linux box at the mo -- having used ctrl-r to recall
> line x in the history, you can't just down-arrow to recall x+1, x+2
> etc. Or can you?
With bash as well as the Python inte
"Tim Golden" <[EMAIL PROTECTED]> writes:
> But as far as I can tell
> from my experience and from the docs -- and I'm not near a
> Linux box at the mo -- having used ctrl-r to recall line x
> in the history, you can't just down-arrow to recall x+1, x+2 etc.
> Or can you?
You can. It works fin
[Sybren Stuvel]
[Tim Golden]
> > It's obvious that everyone has a different way of working, and that
> > I'm more comfortable in Windows because all sorts of small
> > familiarities
> So what I read in your post is that you simply don't want to leave
> your familiar environment. Fair enough.
Wel
"Tim Golden" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED]
>> But command line in Windows is in no way in the same
>> league as *nix shell. Use for command completion and up/down
>> arrow or to search for history.
>
> [darren kirby]
>> Try ctrl-r in bash, then type your first few letters...
>
oops, stand corrected. As I don't use the feature more than ctrl-r and
up/down arrow.
Tim Golden wrote:
> Thanks to both of you. But that much I already knew. It's not
> that I have *no* knowledge about readline: I did at least
> read the manuals when I got stuck! But as far as I can tell
> from m
Tim Golden wrote:
> As it happens, (and I suspect I'll have to don my flameproof suit
here),
> I prefer the Windows command line to bash/readline for day-to-day use,
> including in Python. Why? Because it does what I can't for the life of
> me get readline to do: you can type the first few letters
Tim Golden wrote:
>As it happens, (and I suspect I'll have to don my flameproof suit here),
>I prefer the Windows command line to bash/readline for day-to-day use,
>including in Python. Why? Because it does what I can't for the life of
>me get readline to do: you can type the first few letters
Tim Golden enlightened us with:
> Not quite fair. Not only would I avoid saying something with a
> redundant apostrophe ;) but the Windows user interface, at least for
> my purposes, didn't change such a huge amount between Win9x and
> Win2K,
Hence my reference to windows 3.1.
> It's obvious that
quoth the Tim Golden:
> As it happens, (and I suspect I'll have to don my flameproof suit here),
> I prefer the Windows command line to bash/readline for day-to-day use,
> including in Python. Why? Because it does what I can't for the life of
> me get readline to do: you can type the first few lett
Tim Golden wrote:
> As it happens, (and I suspect I'll have to don my flameproof suit here),
> I prefer the Windows command line to bash/readline for day-to-day use,
> including in Python. Why? Because it does what I can't for the life of
> me get readline to do: you can type the first few letters
[Sybren Stuvel]
Tim Golden enlightened us with:
> > Well, I'm with you. I'm sure a lot of people will chime in to point
> > out just how flexible and useful and productive Linux is as a
> > workstation, but every time I try to use it -- and I make an honest
> > effort -- I end up back in Windows
Background.
I'm running on WinXP w/ MS Services for Unix installed (to give
rsh/rlogin ability), both Python 2.3 and 2.4 version. In linux, I'm
running RHEE with python2.3 version. The code below works fine for me
in linux, but in WinXP the popen*() command "hangs". More
specifically, I get an
93 matches
Mail list logo
