[Python-Dev] FWD: Windows 7 Compatibility

[Aahz]

Still no-mail on python-dev, forwarding this because it has a direct
e-mail contact for Microsoft at the bottom.

- Forwarded message from Joanna Cobb  -

> From: Joanna Cobb 
> To: "webmas...@python.org" 
> Date: Mon, 14 Sep 2009 10:05:34 -0400
> Subject: Windows 7 Compatibility
> 
> Regarding:  Windows 7 Compatibility for Python Software Foundation - 
> Application:  Python
> 
> I am trying to contact your company regarding the Microsoft Windows 7 
> Compatibility Program for Python.  I have not been able to get in touch with 
> the person responsible for this application in your company and this is why I 
> am reaching out to you through the Support Team. This application has been 
> identified as one of the applications Microsoft would like to see supported 
> on Windows 7 and I have been tasked by Microsoft to help answer your 
> questions about Windows 7 application compatibility and help you get your 
> application through the Windows 7 "Green Light" compatibility process.
> 
> If your application already supports Windows Vista, chances are it will 
> already be compatible with Windows 7 without the need for any code changes.  
> By pledging support for Windows 7 you're application will automatically be 
> listed in the Windows Application Compatibility seen currently by more than 1 
> million users per month. The registration is extremely simple and just asks a 
> few key questions.
> 
> Here is the link to Microsoft's ISV Application Compatibility page: 
> http://partner.microsoft.com/isvappcompat.  When you have a moment, I would 
> encourage you to visit the site and complete the process to pledge support 
> for your application on Windows 7 by October 22nd 2009 when Windows 7 is 
> officially released.
> 
> In addition if you are able to pledge compatibility you'll receive access to 
> a special Windows 7 Partner Marketing Kit  that includes a press release with 
> a Microsoft quote, plus customizable marketing templates including; email 
> templates, postcards, web banners, business letter, and copy blocks, all to 
> identify to your customers, or potential customers that your solutions are 
> compatible with Windows 7.
> 
> If you provide me with a phone number where to get in touch with you, I will 
> call you to answer any questions you may have.
> 
> Once you register on the ISV Application Compatibility site, I would 
> appreciate it if you would email me to let me know that you have completed so 
> that I can make a note of it for Microsoft. If you register the application 
> under a different partner or application name please let me know in order to 
> track changes. If there is a new version of the application and there are no 
> plans to support Windows 7 on the older version please register the older 
> version as "No planned Support" on the site as well as the new version with 
> desired Win7 compatibility date.
> 
> Should you have any questions about this email feel free to call me or send 
> an email to my supervisor at  
> v-m...@microsoft.com.
> 
> Best regards,
> 
> Joanna Cobb
> Business Development Representative
> N(3)
> niche cubed
> Office:  800.508.4291 Ext. 316
> joanna.c...@nichecubed.com
> www.nichecubed.com
> 
> Confidentiality note: This e-mail, and any attachment to it, contains 
> privileged and confidential information intended only for the use of the 
> individual(s) or entity named in the e-mail.  If the reader of the e-mail is 
> not the intended recipient, or the employee or agent responsible for 
> delivering it to the intended recipient, you are hereby notified that reading 
> it is strictly prohibited.  If you have received this e-mail in error, please 
> immediately return it to the sender and delete it from your system.  Thank 
> you.
> 

- End forwarded message -

-- 
Aahz (a...@pythoncraft.com)   <*> http://www.pythoncraft.com/

"It's 106 miles to Chicago.  We have a full tank of gas, a half-pack of
cigarettes, it's dark, and we're wearing sunglasses."  "Hit it."
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] PEP 3144 review.

[Guido van Rossum]

What's the opinion of the other interested party or parties? I don't
want a repeat of the events last time, where we had to pull it at the
last time because there hadn't been enough discussion.

On Mon, Sep 14, 2009 at 9:44 AM, Peter Moody  wrote:
> Folks, Guido,
>
> I believe PEP 3144 is ready for your review.  When you get a chance,
> can you take a look/make a pronouncement?
>
> Cheers,
> /peter
>



-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] PEP 3144 review.

[Peter Moody]

Folks, Guido,

I believe PEP 3144 is ready for your review.  When you get a chance,
can you take a look/make a pronouncement?

Cheers,
/peter
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] PEP 3144 review.

[Andrew McNamara]

>I believe PEP 3144 is ready for your review.  When you get a chance,
>can you take a look/make a pronouncement?

In my experience it is common to leave out the masked octets when
referring to an IPv4 network (the octets are assumed to be zero), so I
don't agree with this behaviour from the reference implementation:

>>> ipaddr.IPv4Network('10/8')
IPv4Network('0.0.0.10/8')
>>> ipaddr.IPv4Network('192.168/16')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/src/py/ipaddr/ipaddr.py", line 1246, in __init__
raise IPv4IpValidationError(addr[0])
ipaddr.IPv4IpValidationError: '192.168' is not a valid IPv4 address

I also couldn't see an easy way to get from a network address to the
containing network. For example:

>>> ipaddr.IPv4Network('192.168.1.1/16')
IPv4Network('192.168.1.1/16')

This is close:

>>> ipaddr.IPv4Network('192.168.1.1/16').network
IPv4Address('192.168.0.0')

What I want is a method that returns:

IPv4Network('192.168.0.0/16')

I appreciate these requests are somewhat contradictory (one calls
for masked octets to be insignificant, the other calls for them to be
significant), but they are both valid use cases in my experience.

Apologies if these have already been covered in prior discussion -
I've tried to keep up, but I haven't been able to give it the attention
it deserves.

I also note that many methods in the reference implementation are not
discussed in the PEP. While I don't consider this a problem for the PEP,
anyone reviewing the module for inclusion in the standard lib needs to 
consider them.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] PEP 3144 review.

[Peter Moody]

On Mon, Sep 14, 2009 at 7:11 PM, Andrew McNamara
 wrote:
>>I believe PEP 3144 is ready for your review.  When you get a chance,
>>can you take a look/make a pronouncement?
>
> In my experience it is common to leave out the masked octets when
> referring to an IPv4 network (the octets are assumed to be zero), so I
> don't agree with this behaviour from the reference implementation:

huh, this appears to be a bug. filing an issue and I'll have this
fixed before anything is submitted
(http://code.google.com/p/ipaddr-py/issues/detail?id=35)

>    >>> ipaddr.IPv4Network('10/8')
>    IPv4Network('0.0.0.10/8')
>    >>> ipaddr.IPv4Network('192.168/16')
>    Traceback (most recent call last):
>      File "", line 1, in 
>      File "/usr/src/py/ipaddr/ipaddr.py", line 1246, in __init__
>        raise IPv4IpValidationError(addr[0])
>    ipaddr.IPv4IpValidationError: '192.168' is not a valid IPv4 address
>
> I also couldn't see an easy way to get from a network address to the
> containing network. For example:
>
>    >>> ipaddr.IPv4Network('192.168.1.1/16')
>    IPv4Network('192.168.1.1/16')
>
> This is close:
>
>    >>> ipaddr.IPv4Network('192.168.1.1/16').network
>    IPv4Address('192.168.0.0')
>
> What I want is a method that returns:
>
>    IPv4Network('192.168.0.0/16')

I can see about adding this. you can currently do:

>>> a = ipaddr.IPv4Network('192.168.1.1/16')
>>> '%s/%s' % (a.network, a.prefixlen)
192.168.0.0/16

(I do something very similar to this in address_exclude)

> I appreciate these requests are somewhat contradictory (one calls
> for masked octets to be insignificant, the other calls for them to be
> significant), but they are both valid use cases in my experience.
>
> Apologies if these have already been covered in prior discussion -
> I've tried to keep up, but I haven't been able to give it the attention
> it deserves.

no need to apologize, all comments welcome.

> I also note that many methods in the reference implementation are not
> discussed in the PEP. While I don't consider this a problem for the PEP,
> anyone reviewing the module for inclusion in the standard lib needs to
> consider them.

yeah, I didn't exactly want the PEP to be the pydoc of ipaddr, but I
did want to explain the features and show how I thought they were
important to whatever might be accepted by python. I can certainly go
into much more detail in the PEP if that's deemed important.

Cheers,
/peter

> --
> Andrew McNamara, Senior Developer, Object Craft
> http://www.object-craft.com.au/
>
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Numeric alignment issue with PEP 3101

[Lie Ryan]

Raymond Hettinger wrote:

I concur.  Numbers are naturally right aligned.




Isn't numbers are "naturally right aligned" because of the Big Endian 
notations that most mathematicians currently use. Had we been using 
Little Endian notation, numbers would be naturally left-aligned, 
wouldn't they?


And I sort of disagree with saying it's naturally left- or right- 
aligned; as numbers are naturally (decimal) dot-aligned (if you use dot 
to separate the whole and fractional part of your number).


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Numeric alignment issue with PEP 3101

[Raymond Hettinger]

And I sort of disagree with saying it's naturally left- or right- 
aligned; as numbers are naturally (decimal) dot-aligned (if you use dot 
to separate the whole and fractional part of your number).



How about, "naturally aligned by place value".


Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com