[issue14070] reload(module, ignore_pyc=True) flag
New submission from Tim McNamara : When developing Python code, I often find myself needing to run "rm *.pyc" so that the interpreter will ignore any new changes that I have made to source files. It's really frustrating when forgotten. Adding a flag to the reload builtin would go a long way to simplify this process. -- components: IO messages: 153839 nosy: timClicks priority: normal severity: normal status: open title: reload(module, ignore_pyc=True) flag ___ Python tracker <http://bugs.python.org/issue14070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14070] Idea: Add a flag to reload from source, e.g. reload(module, ignore_pyc=True)
Changes by Tim McNamara : -- title: reload(module, ignore_pyc=True) flag -> Idea: Add a flag to reload from source, e.g. reload(module, ignore_pyc=True) ___ Python tracker <http://bugs.python.org/issue14070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14070] Idea: Add a flag to reload from source, e.g. reload(module, ignore_pyc=True)
Tim McNamara added the comment: No no, I don't want to ignore source files. I want to be able to change a .py file, then reload in the Python shell and for the changes to be applied. At the moment, .pyc files within a project complicate this. -- ___ Python tracker <http://bugs.python.org/issue14070> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34256] Python treats ASCII record seperator ('\x1e as a newline
New submission from Tim McNamara :
Hello,
I apologize if this is expected behavior, however it doesn't appear to be
documented haven't.
>>> "single\x1eline\x1estring".splitlines()
['single', 'line', 'string']
--
messages: 322537
nosy: timClicks
priority: normal
severity: normal
status: open
title: Python treats ASCII record seperator ('\x1e as a newline
versions: Python 3.5, Python 3.6
___
Python tracker
<https://bugs.python.org/issue34256>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34256] Python treats ASCII record seperator ('\x1e') as a newline
Tim McNamara added the comment:
Hello,
I apologize if this is expected behavior, however it doesn't appear to be
documented.
>>> "single\x1eline\x1estring".splitlines()
['single', 'line', 'string']
The glossary refers to the universal newlines as:
> universal newlines
>A manner of interpreting text streams in which all of the
>following are recognized as ending a line: the Unix end-of-line
>convention '\n', the Windows convention '\r\n', and the old
>Macintosh convention '\r'. See PEP 278 and PEP 3116, as well as
>bytes.splitlines() for an additional use.
https://docs.python.org/3/glossary.html#term-universal-newlines
According to Wikipedia, pre-POSIX QNX uses `\x1e` as a newline
(https://en.wikipedia.org/wiki/Newline#Representation), but I don't think that
it should be treated as the default.
--
title: Python treats ASCII record seperator ('\x1e as a newline -> Python
treats ASCII record seperator ('\x1e') as a newline
___
Python tracker
<https://bugs.python.org/issue34256>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
