This looks like a bad idea.  You are weakening the test by removing 
non-ascii chars here.  A better approach would have been to rewrite the 
non-ascii chars using \N (or \u or \U) escapes.

Regards

   - Jacob

Michael Howitz wrote:
> Log message for revision 90434:
>   as it seems impossible to upload umlauts in long_description to pypi using 
> distutils, so I had to replace the umlauts
>
> Changed:
>   U   zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt
>
> -=-
> Modified: zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt
> ===================================================================
> --- zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt     
> 2008-08-27 11:44:57 UTC (rev 90433)
> +++ zc.sourcefactory/trunk/src/zc/sourcefactory/browser/token.txt     
> 2008-08-27 11:49:47 UTC (rev 90434)
> @@ -18,8 +18,8 @@
>  =======
>  
>    >>> zc.sourcefactory.browser.token.fromUnicode(
> -  ...     u'somestring with umlauts öäü')
> -  '45dadc304e0d6ae7f4864368bad74951'
> +  ...     u'somestring with strange chars #*&_;)')
> +  'f33b8a6b56403c9d560e2ef772336798'
>  
>  Integer
>  =======
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Checkins mailing list
> [EMAIL PROTECTED]
> http://mail.zope.org/mailman/listinfo/checkins
>   

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to