Mailman 3 March 2004 - Python-checkins

diplomas for sale from accredited universities
by Edna Delacruz March 28, 2004

March 28, 2004

1 0

python/nondist/sandbox/decimal test_Decimal.py, 1.11, 1.12
by facundobatista＠users.sourceforge.net March 28, 2004

March 28, 2004

Update of /cvsroot/python/python/nondist/sandbox/decimal In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6260 Modified Files: test_Decimal.py Log Message: Added two groups of test classes and corrected some minor try/except issues. Index: test_Decimal.py =================================================================== RCS file: /cvsroot/python/python/nondist/sandbox/decimal/test_Decimal.py,v retrieving revision 1.11 retrieving revision 1.12 diff -C2 -d -r1.11 -r1.12 *** test_Decimal.py 24 Mar 2004 01:57:49 -0000 1.11 --- test_Decimal.py 28 Mar 2004 15:39:38 -0000 1.12 *************** *** 15,25 **** """ ! # 0.1.3 2003.3.23 facundobatista: Added arithmetic operators test and corrected ! # minor method case issues. ! # 0.1.2 2003.3.20 facundobatista: Added from_float to explicit construction test ! # cases and all implicit construction test cases. Also upgraded ! # method names to new GvR definiton. ! # 0.1.1 2003.3.11 facundobatista: Added Explicit Construction tests ! # 0.1.0 2003.3.11 facundobatista: Placed the structure to run separate test groups # ToDo: --- 15,29 ---- """ ! # 0.1.4 2003.03.28 fb: Added Use of Context and Decimal Usability test cases. ! # Corrected tests using try/except/else. ! # 0.1.3 2003.03.23 fb: Added arithmetic operators test and corrected minor ! # method case issues. ! # 0.1.2 2003.03.20 fb: Added from_float to explicit construction test cases ! # and all implicit construction test cases. Also upgraded ! # method names to new GvR definiton. ! # 0.1.1 2003.03.11 fb: Added Explicit Construction tests ! # 0.1.0 2003.03.11 fb: Placed the structure to run separate test groups ! # ! # fb = facundobatista # ToDo: *************** *** 615,619 **** except TypeError: pass ! def test_from_int(self): '''Implicit construction with int or long.''' --- 619,625 ---- except TypeError: pass ! else: ! self.fail('Did not raised an error!') ! def test_from_int(self): '''Implicit construction with int or long.''' *************** *** 629,632 **** --- 635,640 ---- except TypeError: pass + else: + self.fail('Did not raised an error!') def test_from_string(self): *************** *** 639,642 **** --- 647,652 ---- except TypeError: pass + else: + self.fail('Did not raised an error!') def test_from_float(self): *************** *** 649,652 **** --- 659,664 ---- except TypeError: pass + else: + self.fail('Did not raised an error!') def test_from_Decimal(self): *************** *** 901,904 **** --- 913,1141 ---- + # The following are two functions used to test threading in the next class + + def thfunc1(cls): + d1 = Decimal(1) + d3 = Decimal(3) + cls.assertEqual(d1/d3, Decimal('0.333333333')) + cls.event.wait() + cls.assertEqual(d1/d3, Decimal('0.333333333')) + return + + def thfunc2(cls): + d1 = Decimal(1) + d3 = Decimal(3) + cls.assertEqual(d1/d3, Decimal('0.333333333')) + thiscontext = getcontext() + thiscontext.prec = 18 + cls.assertEqual(d1/d3, Decimal('0.333333333333333333')) + cls.event.set() + return + + + class DecimalUseOfContextTest(unittest.TestCase): + '''Unit tests for Use of Context cases in Decimal.''' + + import threading + # Take care executing this test from IDLE, there's an issue in threading + # that hangs IDLE and I couldn't find it + + def test_threading(self): + '''Test the "threading isolation" of a Context.''' + + self.event = threading.Event() + + th1 = threading.Thread(target=thfunc1, args=(self,)) + th2 = threading.Thread(target=thfunc2, args=(self,)) + + th1.start() + th2.start() + return + + + class DecimalUsabilityTest(unittest.TestCase): + '''Unit tests for Usability cases of Decimal.''' + + def test_comparison_operators(self): + '''Testing ==, !=, <, >, <=, >=, cmp.''' + + da = Decimal('23.42') + db = Decimal('23.42') + dc = Decimal('45') + + #two Decimals + self.failUnless(dc > da) + self.failUnless(dc >= da) + self.failUnless(da < dc) + self.failUnless(da <= dc) + self.failUnless(da == db) + self.failUnless(da != dc) + self.failUnless(da <= db) + self.failUnless(da >= db) + self.assertEqual(cmp(dc,da), 1) + self.assertEqual(cmp(da,dc), -1) + self.assertEqual(cmp(da,db), 0) + + #a Decimal and an int + self.failUnless(dc > 23) + self.failUnless(23 < dc) + self.failUnless(dc == 45) + self.assertEqual(cmp(dc,23), 1) + self.assertEqual(cmp(23,dc), -1) + self.assertEqual(cmp(dc,45), 0) + + #a Decimal and a float + self.failUnless(dc > 23.42) + self.failUnless(23.42 < dc) + self.failUnless(da == 23.42) + self.assertEqual(cmp(dc,23.42), 1) + self.assertEqual(cmp(23.42,dc), -1) + self.assertEqual(cmp(da,23.42), 0) + + #a Decimal and uncomparable + self.assertRaises(TypeError, da == 'ugly') + self.assertRaises(TypeError, da == '32.7') + self.assertRaises(TypeError, da == object) + + def test_copy_methods(self): + '''Test copy and deepcopy.''' + + import copy + d = Decimal('43.24') + + #copy + c = copy.copy(d) + self.assertEqual(c, d) + self.assertNotEqual(id(c), id(d)) + + #deepcopy + dc = copy.deepcopy(d) + self.assertEqual(dc, d) + self.assertNotEqual(id(dc), id(d)) + + def test_hash_method(self): + '''Test hash.''' + + #just that it's hashable + hash(Decimal(23)) + + #the same hash that to an int + self.assertEqual(hash(Decimal(23)), hash(23)) + + #the same hash that to an "exact float" + self.assertEqual(hash(Decimal('32.32')), hash(32.32)) + + #the same hash that to an "inexact float" + self.assertEqual(hash(Decimal('23.72')), hash(23.72)) + + def test_minmax_methods(self): + '''Test min and max between Decimal and others.''' + + d1 = Decimal('15.32') + d2 = Decimal('28.5') + l1 = 15 + l2 = 28 + f1 = 15.32 + f2 = 28.5 + + #between Decimals + self.failUnless(min(d1,d2) is d1) + self.failUnless(min(d2,d1) is d1) + self.failUnless(max(d1,d2) is d2) + self.failUnless(max(d2,d1) is d2) + + #between Decimal and long + self.failUnless(min(d1,l2) is d1) + self.failUnless(min(l2,d1) is d1) + self.failUnless(max(l1,d2) is d2) + self.failUnless(max(d2,l1) is d2) + + #between Decimal and float + self.failUnless(min(d1,f2) is d1) + self.failUnless(min(f2,d1) is d1) + self.failUnless(max(f1,d2) is d2) + self.failUnless(max(d2,f1) is d2) + + def test_as_boolean(self): + '''Test that it can be used as boolean.''' + + #as false + self.failIf(Decimal(0)) + + #as true + self.failUnless(Decimal('0.372')) + + def test_tostring_methods(self): + '''Test str and repr methods.''' + + d = Decimal('15.32') + + #str + self.assertEqual(str(d), '15.32') + + #repr + self.assertEqual(repr(d), 'Decimal( (0, (1, 5, 3, 2), -2) )') + + def test_tonum_methods(self): + '''Test float, int and long methods.''' + + d1 = Decimal('66') + d2 = Decimal('15.32') + + #int + self.assertEqual(int(d1), 66) + self.assertEqual(int(d2), 15) + + #long + self.assertEqual(long(d1), 66) + self.assertEqual(long(d2), 15) + + #float + self.assertEqual(float(d1), 66) + self.assertEqual(float(d2), 15.32) + + def test_round_trip(self): + '''Testing that d == eval(repr(d)) with d as Decimal.''' + + #with zero + d = Decimal( (0, (0,), 0) ) + self.assertEqual(d, eval(repr(d))) + + #int + d = Decimal( (1, (4, 5), 0) ) + self.assertEqual(d, eval(repr(d))) + + #float + d = Decimal( (0, (4, 5, 3, 4), -2) ) + self.assertEqual(d, eval(repr(d))) + + #weird + d = Decimal( (1, (4, 3, 4, 9, 1, 3, 5, 3, 4), -25) ) + self.assertEqual(d, eval(repr(d))) + + def test_immutability(self): + '''Try to change internal objects and see if immutable.''' + + d = Decimal(42) + + #the used attributes + try: + d._exp = 20 + d._int = 3 + d._sign = 1 + except TypeError: + pass + else: + self.fail('Did not raised an error!') + + #some new attribute + try: + d.newone = None + except TypeError: + pass + else: + self.fail('Did not raised an error!') + + def test_main(which=None): *************** *** 917,920 **** --- 1154,1160 ---- run_unittest(DecimalImplicitConstructionTest) run_unittest(DecimalArithmeticOperatorsTest) + run_unittest(DecimalUseOfContextTest) + run_unittest(DecimalUsabilityTest) + return

1 0

A healthy balance sheet adds value to the stock price gg qacrqxj rnpz
by Audrey Lacey March 28, 2004

March 28, 2004

1 0

girth?
by Chi Mcgill March 28, 2004

March 28, 2004

Drop the HAMMER on the next bitch you Nail.... http://mecca.abonepha.com/vp5 Click here if you do not wish to be invited again: http://fightnottobesingle.com/remove/?oc=xxxxyyyy

1 0

python/dist/src/Lib socket.py,1.42,1.43
by tim_one＠users.sourceforge.net March 28, 2004

March 28, 2004

Update of /cvsroot/python/python/dist/src/Lib In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3895/lib Modified Files: socket.py Log Message: SF bug 924242: socket._fileobject._getclosed() returns wrong value The .closed property always returned the wrong result. Bugfix candidate! Index: socket.py =================================================================== RCS file: /cvsroot/python/python/dist/src/Lib/socket.py,v retrieving revision 1.42 retrieving revision 1.43 diff -C2 -d -r1.42 -r1.43 *** socket.py 14 Jun 2003 13:30:53 -0000 1.42 --- socket.py 28 Mar 2004 02:20:44 -0000 1.43 *************** *** 218,222 **** def _getclosed(self): ! return self._sock is not None closed = property(_getclosed, doc="True if the file is closed") --- 218,222 ---- def _getclosed(self): ! return self._sock is None closed = property(_getclosed, doc="True if the file is closed")

1 0

python/dist/src/Lib/test test_socket.py, 1.67, 1.68
by tim_one＠users.sourceforge.net March 28, 2004

March 28, 2004

Update of /cvsroot/python/python/dist/src/Lib/test In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3895/lib/test Modified Files: test_socket.py Log Message: SF bug 924242: socket._fileobject._getclosed() returns wrong value The .closed property always returned the wrong result. Bugfix candidate! Index: test_socket.py =================================================================== RCS file: /cvsroot/python/python/dist/src/Lib/test/test_socket.py,v retrieving revision 1.67 retrieving revision 1.68 diff -C2 -d -r1.67 -r1.68 *** test_socket.py 10 Feb 2004 15:51:15 -0000 1.67 --- test_socket.py 28 Mar 2004 02:20:45 -0000 1.68 *************** *** 591,594 **** --- 591,595 ---- def tearDown(self): self.serv_file.close() + self.assert_(self.serv_file.closed) self.serv_file = None SocketConnectedTest.tearDown(self) *************** *** 600,603 **** --- 601,605 ---- def clientTearDown(self): self.cli_file.close() + self.assert_(self.cli_file.closed) self.cli_file = None SocketConnectedTest.clientTearDown(self) *************** *** 646,649 **** --- 648,657 ---- self.cli_file.flush() + def testClosedAttr(self): + self.assert_(not self.serv_file.closed) + + def _testClosedAttr(self): + self.assert_(not self.cli_file.closed) + class UnbufferedFileObjectClassTestCase(FileObjectClassTestCase):

1 0

python/nondist/peps pep-0008.txt,1.22,1.23
by bwarsaw＠users.sourceforge.net March 27, 2004

March 27, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7361 Modified Files: pep-0008.txt Log Message: updated a link Index: pep-0008.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0008.txt,v retrieving revision 1.22 retrieving revision 1.23 diff -C2 -d -r1.22 -r1.23 *** pep-0008.txt 27 Mar 2004 20:14:19 -0000 1.22 --- pep-0008.txt 27 Mar 2004 20:37:02 -0000 1.23 *************** *** 604,609 **** [4] http://www.wikipedia.com/wiki/CamelCase ! [5] Barry's GNU Mailman/mimelib style guide ! http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mimelib/mimelib/STYLEGUIDE.t… --- 604,609 ---- [4] http://www.wikipedia.com/wiki/CamelCase ! [5] Barry's GNU Mailman style guide ! http://barry.warsaw.us/software/STYLEGUIDE.txt

1 0

python/nondist/peps pep-0008.txt,1.21,1.22
by bwarsaw＠users.sourceforge.net March 27, 2004

March 27, 2004

Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2842 Modified Files: pep-0008.txt Log Message: A few more minor updates for the Naming Conventions section: - recommend that all new libraries use the standards, but point out that internal consistency with existing standards is more important. - Use b and B instead of x and X (it's hard to distinguish the case of X in some fonts) - StudlyCaps is another name for CapWords - Re-order list so Function Names are followed by Method Names. Also, added a few blank lines in the Method Names section, and described how underscores should separate words for readability. - Added that double leading underscore is usually only necessary to resolve name conflicts in subclasses. Index: pep-0008.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0008.txt,v retrieving revision 1.21 retrieving revision 1.22 diff -C2 -d -r1.21 -r1.22 *** pep-0008.txt 20 Mar 2004 06:42:29 -0000 1.21 --- pep-0008.txt 27 Mar 2004 20:14:19 -0000 1.22 *************** *** 343,349 **** Naming Conventions ! The naming conventions of Python's library are a bit of a mess, so ! we'll never get this completely consistent -- nevertheless, here ! are some guidelines. Descriptive: Naming Styles --- 343,352 ---- Naming Conventions ! The naming conventions of Python's library are a bit of a mess, so we'll ! never get this completely consistent -- nevertheless, here are the ! currently recommended naming standards. New modules and packages ! (including 3rd party frameworks) should be written to these standards, but ! where an existing library has a different style, internal consistency is ! preferred. Descriptive: Naming Styles *************** *** 355,361 **** The following naming styles are commonly distinguished: ! - x (single lowercase letter) ! - X (single uppercase letter) - lowercase --- 358,364 ---- The following naming styles are commonly distinguished: ! - b (single lowercase letter) ! - B (single uppercase letter) - lowercase *************** *** 368,372 **** - CapitalizedWords (or CapWords, or CamelCase -- so named because ! of the bumpy look of its letters[4]) - mixedCase (differs from CapitalizedWords by initial lowercase --- 371,376 ---- - CapitalizedWords (or CapWords, or CamelCase -- so named because ! of the bumpy look of its letters[4]). This is also sometimes known as ! StudlyCaps. - mixedCase (differs from CapitalizedWords by initial lowercase *************** *** 454,464 **** The trend seems to be toward CapWords exception names. - Function Names - - Function names should be lowercase, possibly with underscores to - improve readability. mixedCase is allowed only in contexts where - that's already the prevailing style (e.g. threading.py), to retain - backwards compatibility. - Global Variable Names --- 458,461 ---- *************** *** 469,485 **** with an underscore to prevent exporting them. Method Names and Instance Variables ! The story is largely the same as for functions. Use lowercase ! for methods accessed by other classes or functions that are part ! of the implementation of an object type. Use one leading ! underscore for "internal" methods and instance variables when ! there is no chance of a conflict with subclass or superclass ! attributes or when a subclass might actually need access to ! them. Use two leading underscores (class-private names, ! enforced by Python 1.4) in those cases where it is important ! that only the current class accesses an attribute. (But realize ! that Python contains enough loopholes so that an insistent user ! could gain access nevertheless, e.g. via the __dict__ attribute.) Designing for inheritance --- 466,494 ---- with an underscore to prevent exporting them. + Function Names + + Function names should be lowercase, possibly with words separated by + underscores to improve readability. mixedCase is allowed only in + contexts where that's already the prevailing style (e.g. threading.py), + to retain backwards compatibility. + Method Names and Instance Variables ! The story is largely the same as for functions; in general use lowercase ! with words separated by underscores to improve readability. Do not use ! a leading underscore for methods accessed by other classes or functions ! that are part of the implementation of an object type. ! ! Use one leading underscore for "internal" methods and instance variables ! when there is no chance of a conflict with subclass or superclass ! attributes or when a subclass might actually need access to them. ! ! Use two leading underscores (class-private names, enforced by Python ! 1.4) in those cases where it is important that only the current class ! accesses an attribute. Realize that Python contains enough loopholes so ! that an insistent user could gain access nevertheless, e.g. via the ! __dict__ attribute. Generally, double leading underscores should be ! used only to avoid name conflicts with attributes in classes designed to ! be subclassed. Designing for inheritance

1 0

python/dist/src/Tools/scripts reindent.py, 1.4, 1.5
by montanaro＠users.sourceforge.net March 27, 2004

March 27, 2004

Update of /cvsroot/python/python/dist/src/Tools/scripts In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18556 Modified Files: reindent.py Log Message: add usage() function, -h(elp) flag and long versions of short flags Index: reindent.py =================================================================== RCS file: /cvsroot/python/python/dist/src/Tools/scripts/reindent.py,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** reindent.py 26 Mar 2002 11:39:26 -0000 1.4 --- reindent.py 27 Mar 2004 18:43:56 -0000 1.5 *************** *** 5,11 **** """reindent [-d][-r][-v] [ path ... ] ! -d Dry run. Analyze, but don't make any changes to, files. ! -r Recurse. Search for all .py files in subdirectories too. ! -v Verbose. Print informative msgs; else no output. Change Python (.py) files to use 4-space indents and no hard tab characters. --- 5,12 ---- """reindent [-d][-r][-v] [ path ... ] ! -d (--dryrun) Dry run. Analyze, but don't make any changes to, files. ! -r (--recurse) Recurse. Search for all .py files in subdirectories too. ! -v (--verbose) Verbose. Print informative msgs; else no output. ! -h (--help) Help. Print this usage information and exit. Change Python (.py) files to use 4-space indents and no hard tab characters. *************** *** 43,46 **** --- 44,52 ---- dryrun = 0 + def usage(msg=None): + if msg is not None: + print >> sys.stderr, msg + print >> sys.stderr, __doc__ + def errprint(*args): sep = "" *************** *** 54,68 **** global verbose, recurse, dryrun try: ! opts, args = getopt.getopt(sys.argv[1:], "drv") except getopt.error, msg: ! errprint(msg) return for o, a in opts: ! if o == '-d': dryrun += 1 ! elif o == '-r': recurse += 1 ! elif o == '-v': verbose += 1 if not args: r = Reindenter(sys.stdin) --- 60,78 ---- global verbose, recurse, dryrun try: ! opts, args = getopt.getopt(sys.argv[1:], "drvh", ! ["dryrun", "recurse", "verbose", "help"]) except getopt.error, msg: ! usage(msg) return for o, a in opts: ! if o in ('-d', '--dryrun'): dryrun += 1 ! elif o in ('-r', '--recurse'): recurse += 1 ! elif o in ('-v', '--verbose'): verbose += 1 + elif o in ('-h', '--help'): + usage() + return if not args: r = Reindenter(sys.stdin)

1 0

python/dist/src/Doc/tut glossary.tex,1.5,1.6
by montanaro＠users.sourceforge.net March 27, 2004

March 27, 2004

Update of /cvsroot/python/python/dist/src/Doc/tut In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14413 Modified Files: glossary.tex Log Message: - add entry for complex number - fix a couple typos - refine definitions for "interpreted" and "coercion" based upon updates on the python glossary wiki Index: glossary.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/tut/glossary.tex,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** glossary.tex 28 Sep 2003 19:03:36 -0000 1.5 --- glossary.tex 27 Mar 2004 18:23:11 -0000 1.6 *************** *** 38,48 **** \index{coercion} \item[coercion] ! Converting data from one type to another. For example, ! {}\code{int(3.15)} coerces the floating point number to the integer, ! {}\code{3}. Most mathematical operations have rules for coercing ! their arguments to a common type. For instance, adding \code{3+4.5}, ! causes the integer \code{3} to be coerced to be a float ! {}\code{3.0} before adding to \code{4.5} resulting in the float ! {}\code{7.5}. \index{descriptor} --- 38,68 ---- \index{coercion} \item[coercion] ! ! The implicit conversion of an instance of one type to another during an ! operation which involves two arguments of the same type. For example, ! {}\code{int(3.15)} converts the floating point number to the integer, ! {}\code{3}, but in {}\code{3+4.5}, each argument is of a different type (one ! int, one float), and both must be converted to the same type before they can ! be added or it will raise a {}\code{TypeError}. Coercion between two ! operands can be performed with the {}\code{coerce} builtin function; thus, ! {}\code{3+4.5} is equivalent to calling {}\code{operator.add(*coerce(3, ! 4.5))} and results in {}\code{operator.add(3.0, 4.5)}. Without coercion, ! all arguments of even compatible types would have to be normalized to the ! same value by the programmer, e.g., {}\code{float(3)+4.5} rather than just ! {}\code{3+4.5}. ! ! \index{complex number} ! \item[complex number] ! ! An extension of the familiar real number system in which all numbers are ! expressed as a sum of a real part and an imaginary part. Imaginary numbers ! are real multiples of the imaginary unit (the square root of {}\code{-1}), ! often written {}\code{i} in mathematics or {}\code{j} in engineering. ! Python has builtin support for complex numbers, which are written with this ! latter notation; the imaginary part is written with a {}\code{j} suffix, ! e.g., {}\code{3+1j}. To get access to complex equivalents of the ! {}\module{math} module, use {}\module{cmath}. Use of complex numbers is a ! fairy advanced mathematical feature. If you're not aware of a need for it's ! almost certain you can safely ignore them. \index{descriptor} *************** *** 100,111 **** \index{generator} \item[generator] ! A function that returns an iterator. It looks like a normal function ! except that the \keyword{yield} keyword is used instead of ! {}\keyword{return}. Generator functions often contain one or more ! {}\keyword{for} or \keyword{while} loops that \keyword{yield} elements ! back to the caller. The function execution is stopped at the ! {}\keyword{yield} keyword (returning the result) and is resumed there ! when the next element is requested by calling the \method{next()} ! method of the returned iterator. \index{GIL} --- 120,131 ---- \index{generator} \item[generator] ! A function that returns an iterator. It looks like a normal function except ! that values are returned to the caller using a \keyword{yield} statement ! instead of a {}\keyword{return} statement. Generator functions often ! contain one or more {}\keyword{for} or \keyword{while} loops that ! \keyword{yield} elements back to the caller. The function execution is ! stopped at the {}\keyword{yield} keyword (returning the result) and is ! resumed there when the next element is requested by calling the ! \method{next()} method of the returned iterator. \index{GIL} *************** *** 135,139 **** \index{immutable} \item[immutable] ! A object with fixed value. Immutable objects are numbers, strings or tuples (and more). Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an --- 155,159 ---- \index{immutable} \item[immutable] ! An object with fixed value. Immutable objects are numbers, strings or tuples (and more). Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an *************** *** 150,154 **** However, if one of the operands is another numeric type (such as a {}\class{float}), the result will be coerced (see \emph{coercion}) to ! a common type. For example, a integer divided by a float will result in a float value, possibly with a decimal fraction. Integer division can be forced by using the \code{//} operator instead of the \code{/} --- 170,174 ---- However, if one of the operands is another numeric type (such as a {}\class{float}), the result will be coerced (see \emph{coercion}) to ! a common type. For example, an integer divided by a float will result in a float value, possibly with a decimal fraction. Integer division can be forced by using the \code{//} operator instead of the \code{/} *************** *** 165,173 **** \index{interpreted} \item[interpreted] ! Python is an interpreted language, opposed to a compiled one. This ! means that the source files can be run right away without first making ! an executable which is then run. Interpreted languages typically have ! a shorter development/debug cycle than compiled ones. See also ! {}\emph{interactive}. \index{iterable} --- 185,193 ---- \index{interpreted} \item[interpreted] ! Python is an interpreted language, as opposed to a compiled one. This means ! that the source files can be run directly without first creating an ! executable which is then run. Interpreted languages typically have a ! shorter development/debug cycle than compiled ones, though their programs ! generally also run more slowly. See also {}\emph{interactive}. \index{iterable}

1 0