Python Forum
Thread Rating:
  • 1 Vote(s) - 2 Average
  • 1
  • 2
  • 3
  • 4
  • 5
getting started, again
#20
(Jul-21-2018, 04:36 PM)bluedoor5 Wrote: That's one way logging I will be using in future, add to next line method
The other type of logging is the over-write.
Also, if "my-text-file.txt" does not exist, it makes one.

(Jul-21-2018, 04:36 PM)bluedoor5 Wrote:
with open(r'C:\MYPYTHONSKOOL\my-text-file.txt', 'a+') as f_out:

The second argument to open is what mode you're opening the file in. "r" is for read-only (you can't write to the file), "w" is for write (and it erases whatever used to be in the file), "a" is for append (you can write, and whatever you write is at the end of the file [...unless you call seek() first...]).

For future reference, the builtin function help can be used to see the docs for something. That normally explains the available options and what they mean. For example, here's open():
>>> help(open)
Help on built-in function open in module io:

open(file, mode='r', buffering=-1, encoding=None, errors=None, newline=None, closefd=True, opener=None)
    Open file and return a stream.  Raise IOError upon failure.

    file is either a text or byte string giving the name (and the path
    if the file isn't in the current working directory) of the file to
    be opened or an integer file descriptor of the file to be
    wrapped. (If a file descriptor is given, it is closed when the
    returned I/O object is closed, unless closefd is set to False.)

    mode is an optional string that specifies the mode in which the file
    is opened. It defaults to 'r' which means open for reading in text
    mode.  Other common values are 'w' for writing (truncating the file if
    it already exists), 'x' for creating and writing to a new file, and
    'a' for appending (which on some Unix systems, means that all writes
    append to the end of the file regardless of the current seek position).
    In text mode, if encoding is not specified the encoding used is platform
    dependent: locale.getpreferredencoding(False) is called to get the
    current locale encoding. (For reading and writing raw bytes use binary
    mode and leave encoding unspecified.) The available modes are:

    ========= ===============================================================
    Character Meaning
    --------- ---------------------------------------------------------------
    'r'       open for reading (default)
    'w'       open for writing, truncating the file first
    'x'       create a new file and open it for writing
    'a'       open for writing, appending to the end of the file if it exists
    'b'       binary mode
    't'       text mode (default)
    '+'       open a disk file for updating (reading and writing)
    'U'       universal newline mode (deprecated)
    ========= ===============================================================

    The default mode is 'rt' (open for reading text). For binary random
    access, the mode 'w+b' opens and truncates the file to 0 bytes, while
    'r+b' opens the file without truncation. The 'x' mode implies 'w' and
    raises an `FileExistsError` if the file already exists.

    Python distinguishes between files opened in binary and text modes,
    even when the underlying operating system doesn't. Files opened in
    binary mode (appending 'b' to the mode argument) return contents as
    bytes objects without any decoding. In text mode (the default, or when
    't' is appended to the mode argument), the contents of the file are
    returned as strings, the bytes having been first decoded using a
    platform-dependent encoding or using the specified encoding if given.

    'U' mode is deprecated and will raise an exception in future versions
    of Python.  It has no effect in Python 3.  Use newline to control
    universal newlines mode.

    buffering is an optional integer used to set the buffering policy.
    Pass 0 to switch buffering off (only allowed in binary mode), 1 to select
    line buffering (only usable in text mode), and an integer > 1 to indicate
    the size of a fixed-size chunk buffer.  When no buffering argument is
    given, the default buffering policy works as follows:

    * Binary files are buffered in fixed-size chunks; the size of the buffer
      is chosen using a heuristic trying to determine the underlying device's
      "block size" and falling back on `io.DEFAULT_BUFFER_SIZE`.
      On many systems, the buffer will typically be 4096 or 8192 bytes long.
-- More  --
Reply


Messages In This Thread
getting started, again - by bluedoor5 - Jul-13-2018, 05:32 AM
RE: getting started, again - by bluedoor5 - Jul-13-2018, 09:06 AM
RE: getting started, again - by snippsat - Jul-13-2018, 10:50 AM
RE: getting started, again - by bluedoor5 - Jul-13-2018, 12:38 PM
RE: getting started, again - by bluedoor5 - Jul-16-2018, 10:00 PM
RE: getting started, again - by snippsat - Jul-16-2018, 10:45 PM
RE: getting started, again - by bluedoor5 - Jul-19-2018, 08:39 PM
RE: getting started, again - by nilamo - Jul-19-2018, 08:48 PM
RE: getting started, again - by bluedoor5 - Jul-19-2018, 09:06 PM
RE: getting started, again - by nilamo - Jul-19-2018, 09:07 PM
RE: getting started, again - by bluedoor5 - Jul-19-2018, 09:44 PM
RE: getting started, again - by bluedoor5 - Jul-20-2018, 10:08 AM
RE: getting started, again - by snippsat - Jul-20-2018, 11:00 AM
RE: getting started, again - by bluedoor5 - Jul-20-2018, 10:47 PM
RE: getting started, again - by bluedoor5 - Jul-21-2018, 03:18 AM
RE: getting started, again - by snippsat - Jul-21-2018, 06:50 AM
RE: getting started, again - by bluedoor5 - Jul-21-2018, 02:44 PM
RE: getting started, again - by snippsat - Jul-21-2018, 03:29 PM
RE: getting started, again - by bluedoor5 - Jul-21-2018, 04:36 PM
RE: getting started, again - by nilamo - Jul-23-2018, 06:00 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  getting started b4iknew 3 2,606 Jan-22-2019, 09:12 AM
Last Post: b4iknew

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020