Mike Driscoll wrote:
I was looking at the front page and thought it might be nice to have a
section devoted to Networking / Remote Access. Or maybe that's rolled
into one of the other categories and I missed it.
Sounds good.
In the "building and deploying" section, I see you have MinGW. I hav
Tim Golden wrote:
[Ton van
Vliet]
IMHO the links could be a bit more visible.
When looking at the 'Where do I begin' paragraph, it took me quite
some time to notice that there *were* actually links in there (after
being taken there by clicking on the 'Where do I begin' link in the
left hand
[Ton van Vliet]
IMHO the links could be a bit more visible.
When looking at the 'Where do I begin' paragraph, it took me quite some
time to notice that there *were* actually links in there (after being
taken there by clicking on the 'Where do I begin' link in the left hand
column already seve
On Thu, 22 May 2008 17:21:47 +0100, you wrote:
>I have a request of the python-win32 community. Have a look at:
>
>http://timgolden.me.uk/python-on-windows/
>
>In particular, click through to the section on the Registry
>(which is the only section which has anything useful in it!)
>and then tell
Tim Golden wrote:
I have a request of the python-win32 community. Have a look at:
http://timgolden.me.uk/python-on-windows/
In particular, click through to the section on the Registry (which is
the only section which has anything useful in it!)
and then tell me what you think. About anything.
Vernon,
Tim:
I think you missed my point...
As you say, the PEP8 style guide "is a starting point for new Python
coders."
That is precisely why it ought to be followed in sample code.
I normally format my function calls exactly the way you do, and I do
so in open source code which I contri
Vernon Cole wrote:
Tim:
I think you missed my point...
As you say, the PEP8 style guide "is a starting point for new Python
coders."
That is precisely why it ought to be followed in sample code.
I normally format my function calls exactly the way you do, and I do
so in open source code whic
wever you want it.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vernon Cole
Sent: Wednesday, May 28, 2008 1:56 PM
To: Python-Win32 List
Subject: Re: [python-win32] Request for comments - the spaces issue
Tim:
I think you missed my point...
A
Tim:
I think you missed my point...
As you say, the PEP8 style guide "is a starting point for new Python
coders."
That is precisely why it ought to be followed in sample code.
I normally format my function calls exactly the way you do, and I do so in
open source code which I contribute to the co
Vernon Cole wrote:
Let's not loose track of the thread here.
The question was whether there should be a space between the function
name and the leading parenthesis, as:
my_function (arg)
vs:
my_function(arg)
PEP8 clearly requires the latter.
IMHO any published example code, which is what
Vernon Cole wrote:
Let's not loose track of the thread here.
The question was whether there should be a space between the function
name and the leading parenthesis, as:
my_function (arg)
vs:
my_function(arg)
PEP8 clearly requires the latter.
PEP8 is a coding standard document for the Pyt
Let's not loose track of the thread here.
The question was whether there should be a space between the function name
and the leading parenthesis, as:
my_function (arg)
vs:
my_function(arg)
PEP8 clearly requires the latter.
IMHO any published example code, which is what we are talking about he
bob gailer wrote:
Tim Roberts wrote:
bob gailer wrote:
Mark Hammond wrote:
In general, I *try* and stick to the Python Style Guide
(http://www.python.org/dev/peps/pep-0008/)
Interesting. I don't like the idea of 2 spaces after a period.
Internet research on this topic seems to favor one spa
Tim Roberts wrote:
bob gailer wrote:
Mark Hammond wrote:
In general, I *try* and stick to the Python Style Guide
(http://www.python.org/dev/peps/pep-0008/)
Interesting. I don't like the idea of 2 spaces after a period.
Internet research on this topic seems to favor one space.
I'm not sure
Tim Golden wrote:
Mike
Driscoll wrote:
Tim Golden wrote:
Yes, I tried that to see what you meant. I'm not sure there's
much I'm going to be able to do about that, unless someone
jumps in with a solution. My main point about the examples is
that they're self-contained. (ie you don't need to prea
bob gailer wrote:
Mark Hammond wrote:
In general, I *try* and stick to the Python Style Guide
(http://www.python.org/dev/peps/pep-0008/)
Interesting. I don't like the idea of 2 spaces after a period.
Internet research on this topic seems to favor one space.
I'm not sure where you got that.
TimG writes:
> That's fine for two lines, but I can't change a whole script to work
> that way :) The intepreter window in PythonWin just doesn't work
> the same way as the conventional console-based one, it seems.
Yeah - it is pretty dumb. I'd love to make pythonwin smarter in this regard
thoug
Mike Driscoll wrote:
Tim Golden wrote:
Yes, I tried that to see what you meant. I'm not sure there's
much I'm going to be able to do about that, unless someone
jumps in with a solution. My main point about the examples is
that they're self-contained. (ie you don't need to prearrange
any data or
Tim Golden wrote:
bob
gailer wrote:
Tim Roberts wrote:
bob gailer wrote:
Please omit the space before ( in code. I find that very
distracting. Example:
print result.Properties_ ("sValue").Value # current
print result.Properties_("sValue").Value # preferred, and how most
code I've seen lo
bob gailer wrote:
Mark Hammond wrote:
In general, I *try* and stick to the Python Style Guide
(http://www.python.org/dev/peps/pep-0008/)
Interesting. I don't like the idea of 2 spaces after a period. Internet
research on this topic seems to favor one space.
As it happens I'm with you on thi
> Interesting. I don't like the idea of 2 spaces after a period.
> Internet research on this topic seems to favor one space.
>
> I notice when a PEP is set in monospace there are 2 spaces after
> periods, otherwise 1 space. That seems inconsistent.
It's not as inconsistent as might seem, as the
Mark Hammond wrote:
In general, I *try* and stick to the Python Style Guide
(http://www.python.org/dev/peps/pep-0008/)
Interesting. I don't like the idea of 2 spaces after a period. Internet
research on this topic seems to favor one space.
I notice when a PEP is set in monospace there are 2
Great site. I like the idea and am going to start posting some code..
On Sat, May 24, 2008 at 9:12 PM, Tim Golden <[EMAIL PROTECTED]> wrote:
> bob gailer wrote:
>
>> Tim Roberts wrote:
>>
>>> bob gailer wrote:
>>>
Please omit the space before ( in code. I find that very distracting.
>>>
In general, I *try* and stick to the Python Style Guide
(http://www.python.org/dev/peps/pep-0008/), particularly for new code. This
makes it easier to contribute code to Python itself, and a number of other
projects (eg bzr) have a policy that requires contributed code conform (and
indeed, they ma
bob gailer wrote:
Tim Roberts wrote:
bob gailer wrote:
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ ("sValue").Value # current
print result.Properties_("sValue").Value # preferred, and how most
code I've seen looks.
Do you under
Len Remmerswaal wrote:
Tim,
Could you add "up" buttons to the "previous|next" lines? I always use
that type of button to regain my bearings in the multitude of pages.
Also I miss a possibility to walk from the start page to all pages
linearly, if I feel like browsing the lot.
Especially on page
bob gailer wrote:
Tim Golden wrote:
[snip]
Likewise I imagine there are many who find my two-spaces
indent style cluttered while I find even four and certainly any
more to be grotesquely elongated.
I also prefer the 2 space indent!
I also realize that when I wrote my previous reply I was n
Tim Golden wrote:
[snip]
Likewise I imagine there are many who find my two-spaces
indent style cluttered while I find even four and certainly any
more to be grotesquely elongated.
I also prefer the 2 space indent!
I also realize that when I wrote my previous reply I was not conscious
that
Tim,
Could you add "up" buttons to the "previous|next" lines? I always use
that type of button to regain my bearings in the multitude of pages.
Also I miss a possibility to walk from the start page to all pages
linearly, if I feel like browsing the lot.
Especially on page one, it seems there are
Tim Roberts wrote:
bob gailer wrote:
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ ("sValue").Value # current
print result.Properties_("sValue").Value # preferred, and how most
code I've seen looks.
Do you understand that this is
lto:[EMAIL PROTECTED] On Behalf Of Tim Golden
Sent: Saturday, May 24, 2008 4:28 AM
Cc: Python-Win32 List
Subject: Re: [python-win32] Request for comments - the spaces issue
[bob gailer]
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ ("
win32] Request for comments - the spaces issue
[bob gailer]
>> Please omit the space before ( in code. I find that very distracting.
>> Example:
>>
>> print result.Properties_ ("sValue").Value # current
>>
>> print result.Properties_("sValue&qu
[bob gailer]
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ ("sValue").Value # current
print result.Properties_("sValue").Value # preferred, and how most
code I've seen looks.
[Tim Roberts]
Do you understand that this is strictly a pe
bob gailer wrote:
You said "you can drop them straight onto an interpreter window and run
them"
It would be quite nice if the Python for Windows Interactive Window also
worked that way. Unfortunately copying your examples and pasting there
does NOT work, and that has always been a pain in the
Dahlstrom, Roger wrote:
My only suggestion was that the navigation was a bit
> inconsistent on the front page - I had to scroll down
> to see what the "contents" were - the "registry"
section was hidden at first. I would have expected
> that to be in the upper left with the rest of the nav.
ction was hidden at first. I would have expected that to be in the upper
left with the rest of the nav.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Roberts
Sent: Friday, May 23, 2008 7:15 PM
To: Python-Win32 List
Subject: Re: [python-win32]
bob gailer wrote:
Please omit the space before ( in code. I find that very distracting.
Example:
print result.Properties_ ("sValue").Value # current
print result.Properties_("sValue").Value # preferred, and how most
code I've seen looks.
Do you understand that this is strictly a personal
Tim Golden wrote:
I have a request of the python-win32 community. Have a look at:
http://timgolden.me.uk/python-on-windows/
In particular, click through to the section on the Registry (which is
the only section which has anything useful in it!)
and then tell me what you think.
Thanks for a
On Fri, May 23, 2008 at 2:21 PM, Tim Golden <[EMAIL PROTECTED]> wrote:
> Kevin Horn wrote:
>
> Sphinx can auto-create "Prev" and "Next" links, which might be useful.
>>
>
> Unless I misunderstand you, I think it's doing that, both across
> the top Navigation bar and along the left sidebar. Or did
Kevin Horn wrote:
I'd like to see a little more prose to go with the examples, not just
code.
No too much, but enough that the reader can understand WHY a certain task i
s done a certain way (and maybe why you would want to do it in the first
place).
Thanks for this input Kevin. Would you min
On Thu, May 22, 2008 at 11:21 AM, Tim Golden <[EMAIL PROTECTED]> wrote:
> I have a request of the python-win32 community. Have a look at:
>
> http://timgolden.me.uk/python-on-windows/
>
Wow, Tim! Thanks for doing this.
> In particular, click through to the section on the Registry (which is the
Hi!
For IPC.Mailslot, if you need, you can look my little example-code (below).
Tested for compatibility with Vista.waitfor.exe ; and tested XP <=>
Vista via LAN
(sorry for my bad english)
@-salutations
--
Michel Claveau
# -*- coding: cp1252 -*-
def mailslotserver(duree=99, syste
On Thu, May 22, 2008 at 6:21 PM, Tim Golden <[EMAIL PROTECTED]> wrote:
> I have a request of the python-win32 community. Have a look at:
>
> http://timgolden.me.uk/python-on-windows/
>
> In particular, click through to the section on the Registry (which is the
> only section which has anything use
Tim,
Some ideas for high-level sections:
- Creating COM components
- Interfacing to COM components
- Creating NT services
- Sending/receiving Windows messages
- Interfacing to the clipboard
- Interfacing to DDE
- Monitoring processes (Task Manager stats on a process)
- Reading/writing NT Event lo
Michael Foord wrote:
Hello Tim,
I posted the link on Twitter, and got a response back asking if there
would be documentation on deployment - py2exe, PyInstaller etc.
Whilst I doubt you can be expected to be a fount of *all* knowledge,
perhaps links or summaries of these topics could be good.
Hello Tim,
I posted the link on Twitter, and got a response back asking if there
would be documentation on deployment - py2exe, PyInstaller etc.
Whilst I doubt you can be expected to be a fount of *all* knowledge,
perhaps links or summaries of these topics could be good.
Michael Foord
http:
Hello Tim,
That looks really good!
Michael
Tim Golden wrote:
I have a request of the python-win32 community. Have a look at:
http://timgolden.me.uk/python-on-windows/
In particular, click through to the section on the Registry (which is
the only section which has anything useful in it!)
an
Tim,
1. Layout (color, font, margins) looks great.
2. Home page:
a. Include a next (page) link in header/footer?
b. Include an about page with brief note about site's reStructuredText
markup and Sphinx. Include a brief description of the Show Source links
(cool!).
3. Getting Started page:
a.
I have a request of the python-win32 community. Have a look at:
http://timgolden.me.uk/python-on-windows/
In particular, click through to the section on the Registry
(which is the only section which has anything useful in it!)
and then tell me what you think. About anything. The contents,
the
49 matches
Mail list logo
