Re: [Python-Dev] Something like PEP-0304 - suppress *.pyc generation
On Mon, Apr 20, 2009 at 12:25 PM, Steven D'Aprano wrote: > On Mon, 20 Apr 2009 04:54:15 pm christian.d...@basf.com wrote: > >> I need something to suppress the generation of *.pyc files >> because i have very much different machines which call a python >> program at same time. > > This list is for development *of* Python, not development *with* > Python. You would probably be better off on comp.lang.python or > python-l...@python.org. > > However, I believe that the normal way to prevent the generation > of .pyc files is to remove write access to the directory where > the .py files are. Checkout http://docs.python.org/using/cmdline.html#envvar-PYTHONDONTWRITEBYTECODE Regards. -- İsmail DÖNMEZ ___ 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] py3k branch still using -fno-strict-aliasing
Hi,
I remember discussing this before and coming to conclusion that
-fno-strict-aliasing would be removed from py3k CFLAGS. But as of now
its still used.
I tested with gcc 4.3.1 on Linux x86_64 and there is no strict
aliasing warning when this flag is removed. Also make testall passes.
Is there any reason to keep this flag? If not see the attached patch.
Regards,
ismail
--
Programmer Excuses number 45: I do object-oriented programming - if
the customer objects, I do more programming.
Index: configure.in
===
--- configure.in (revision 64653)
+++ configure.in (working copy)
@@ -785,23 +785,6 @@
# tweak BASECFLAGS based on compiler and platform
case $GCC in
yes)
-# Python violates C99 rules, by casting between incompatible
-# pointer types. GCC may generate bad code as a result of that,
-# so use -fno-strict-aliasing if supported.
-AC_MSG_CHECKING(whether $CC accepts -fno-strict-aliasing)
- ac_save_cc="$CC"
- CC="$CC -fno-strict-aliasing"
- AC_TRY_RUN([int main() { return 0; }],
- ac_cv_no_strict_aliasing_ok=yes,
- ac_cv_no_strict_aliasing_ok=no,
- ac_cv_no_strict_aliasing_ok=no)
- CC="$ac_save_cc"
-AC_MSG_RESULT($ac_cv_no_strict_aliasing_ok)
-if test $ac_cv_no_strict_aliasing_ok = yes
-then
- BASECFLAGS="$BASECFLAGS -fno-strict-aliasing"
-fi
-
# if using gcc on alpha, use -mieee to get (near) full IEEE 754
# support. Without this, treatment of subnormals doesn't follow
# the standard.
___
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] Unicode 5.1.0
Hi, On Thu, Aug 21, 2008 at 23:35, Guido van Rossum <[EMAIL PROTECTED]> wrote: > I was just paid a visit by my Google colleague Mark Davis, co-founder > of the Unicode project and the president of the Unicode Consortium. He > would like to see improved Unicode support for Python. (Well duh. :-) > On his list of top priorities are: > > 1. Upgrade the unicodata module to the Unicode 5.1.0 standard > 2. Extende the unicodedata module with some additional properties > 3. Add support for Unicode properties to the regex syntax, including > Boolean combinations Adding support for SpecialCasing rules[0] would be good for full Unicode support too. It would fix i/I problems that are currently going on with Turkish locale. [0] http://unicode.org/Public/UNIDATA/SpecialCasing.txt Regards, ismail -- Programmer Excuse #17: The processor stack spring has worn out. ___ 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] Looking for VCS usage scenarios
Hi, On Mon, Nov 3, 2008 at 20:45, Jesse Noller <[EMAIL PROTECTED]> wrote: [...] > I don't see how git can be considered given poor windows support - > compilation on OS/X can be a bear too. I use git on Linux/Mac/Windows day to day, see http://code.google.com/p/git-osx-installer/ http://code.google.com/p/msysgit/ Regards, ismail ___ 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] teaching the new urllib
Hi, On Tue, Feb 3, 2009 at 21:56, Brett Cannon wrote: > Probably the biggest issue will be having to explain string encoding. > Obviously you can gloss over it or provide students with a simple > library that just automatically converts the strings. Or even better, > provide some code for the standard library that can take the HTML, > figure out the encoding, and then return the decoded strings (might > actually already be something for that that I am not aware of). http://chardet.feedparser.org/ should work fine for most auto-encoding detection needs. Regards, ismail ___ 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
