[issue46958] json dump/dumps prints each array element on a new line (bad for readability)

Change by Daniel : -- keywords: +patch pull_requests: +29873 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31762 ___ Python tracker ___

[issue46958] json dump/dumps prints each array element on a new line (bad for readability)

Change by Daniel : -- components: Library (Lib) nosy: Entirity priority: normal severity: normal status: open title: json dump/dumps prints each array element on a new line (bad for readability) type: enhancement versions: Python 3.11 ___ Python

[Python-announce] Brand new: Line Profiler GUI v0.1

Hi all, In the dark moments of code optimization, line_profiler from Robert Kern (now https://github.com/pyutils/line_profiler) helped me a lot. To ease the usage of this tool I created a GUI, namely "Line Profiler GUI". The installation is just a pip command away (choose your favorite python Qt

Re: Breaking new relic format on a new line character in FileHandler appender

;INFO", "log.entity.name":"my-service-name", "message":"test"} This issue occurs when a new line is present in the message property of the log i.e. on any error we have a message like "Traceback (most recent call last):" which represents an err

Re: Breaking new relic format on a new line character in FileHandler appender

On Thu, Nov 11, 2021 at 5:00 PM Vijay Karavadra via Python-list wrote: > > Hello Team, > > I'm trying to add logs in the new relic platform from a python application. > For that, I've to add logs in a local file in a specific format which is > > '{"log.level":"%(levelname)s",

Breaking new relic format on a new line character in FileHandler appender

uot;%(message)s"}' This works fine in normal scenario and generates the below type of line in log file and logs are added to new relic with expected properties set like log level, entity name, message etc. {"log.level":"INFO", "log.entity.name":"my-service-

[issue26503] argparse with required field , not having new line separator in -help dispaly

Irit Katriel added the comment: issue11874 has been fixed and its PR has a unit test that seems similar to the case reported here (test_help_with_metavar). If you are still seeing this issue on 3.9 or higher, please create a new issue and include a code snippet that reproduces the problem.

[issue42875] argparse incorrectly shows help string on a new line in case of long command string

paul j3 added the comment: This issue is discussed in: https://bugs.python.org/issue34724 argparse subparser help indent too short and https://stackoverflow.com/questions/3215/max-help-position-is-not-works-in-python-argparse-library -- ___

[issue42875] argparse incorrectly shows help string on a new line in case of long command string

Change by Pavel Ditenbir : -- versions: -Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42875] argparse incorrectly shows help string on a new line in case of long command string

Change by Pavel Ditenbir : -- versions: +Python 3.10, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ ___

[issue42875] argparse incorrectly shows help string on a new line in case of long command string

Change by hai shi : -- nosy: +paul.j3, rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42875] argparse incorrectly shows help string on a new line in case of long command string

Change by Pavel Ditenbir : -- keywords: +patch pull_requests: +23003 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24177 ___ Python tracker ___

[issue42875] argparse incorrectly shows help string on a new line in case of long command string

priority: normal severity: normal status: open title: argparse incorrectly shows help string on a new line in case of long command string type: behavior versions: Python 3.9 Added file: https://bugs.python.org/file49730/argparse-indent-sample.py ___ Python tracker

[issue41881] New Line escape issue in raw strings

Change by Kevin Ardath : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue41881] New Line escape issue in raw strings

Serhiy Storchaka added the comment: It is expected behavior. \n in a raw string means two characters, backslash and "n", not a single newline character. Use non-raw string to embed a newline character. -- nosy: +serhiy.storchaka ___ Python

[issue41881] New Line escape issue in raw strings

New submission from Kevin Ardath : When attempting to concatenate some strings with a new line, I observed that formatting braces in a raw string skipped a new line escape: print(r'{{}}\nx'.format()) Produces: {}\nx Rather than: {} x -- messages: 377624 nosy: ardath.kevin priority

[issue37182] ast - handling new line inside a string

Eric V. Smith added the comment: There was a recent discussion about this on the bug tracker, but of course now I can't find it. But for an earlier discussion, see issue 25885. The decision was that your expectation that the nodes be distinguishable isn't a design goal of the ast. There's

[issue37182] ast - handling new line inside a string

Ilya Kamenshchikov added the comment: Same problem holds for tabs (\\t vs \t). For \\r vs \r, it is even more fun: txt1 = '"""\\r"""' txt2 = '"""\r"""' >>> b'\r' >>> b'\n' -- ___ Python tracker

[issue37182] ast - handling new line inside a string

-- components: Library (Lib) messages: 344861 nosy: Ilya Kamenshchikov priority: normal severity: normal status: open title: ast - handling new line inside a string type: behavior versions: Python 3.7

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

Eric V. Smith added the comment: I agree with Mark: the string is being correctly interpreted by the AST parser, per Python's tokenizer rules. You might want to look at lib2to3, which I think is also used by black. It's also possible that mypy or another static analyzer would be using some

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

Mark Dickinson added the comment: The AST _does_ correctly represent the Python string object in the source, though. After: >>> s = """ ... Hello \n world ... """ we have a Python object `s` of type `str`, which contains exactly three newlines, zero "n" characters, and zero backslashes.

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

Amber Brown added the comment: There's a difference between round-tripping back to the source text and correctly representing the text in the source, though. Since I'm using this module to perform static analysis of a Python module to retrieve class/function definitions and their docstrings

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

Eric V. Smith added the comment: The existing behavior is what I'd expect. Using python3: >>> import ast >>> s = open('file.py', 'rb').read() >>> s b'"""\nHello \\n blah.\n"""\n' >>> ast.dump(ast.parse(s)) "Module(body=[Expr(value=Str(s='\\nHello \\n blah.\\n'))])" >>> eval(s) '\nHello \n

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

Matthias Bussonnier added the comment: I believe this one is even before the ast, in the tokenizer. Though the AST is also doing some normalisation in identifiers (“ε” U+03B5 Greek Small Letter Epsilon Unicode Character , and “ϵ” U+03F5 Greek Lunate Epsilon Symbol Unicode Character get

[issue36911] ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (literal new line) and the ASCII codepoints 134 and 156 ("\n")

aviour: ``` >>> repr(f.body[0].value.s) "'\\nHello n blah.\\n'" ``` -- components: Library (Lib) messages: 342417 nosy: hawkowl priority: normal severity: normal status: open title: ast.parse outputs ast.Strs which do not differentiate between the ASCII codepoint 12 (

Re: cleaner version of variable, new line

On Thursday, May 24, 2018 at 8:51:07 PM UTC-4, asa3...@gmail.com wrote: > hi just seeing if there is a cleaner way to write this. > > s1= "kitti" > s2= 'kitti' > i= 3 > print(s1+ "\n" + "="*i + "^" + "\n" +s2) > > > > kitti > ===^ > kitti more legible that way... thks --

Re: cleaner version of variable, new line

On Thu, 24 May 2018 17:50:53 -0700, asa32sd23 wrote: > hi just seeing if there is a cleaner way to write this. > > s1= "kitti" > s2= 'kitti' > i= 3 > print(s1+ "\n" + "="*i + "^" + "\n" +s2) s = "kitti" i = 3 print(s, "="*i + "^", s, sep='\n') -- Steve --

Re: cleaner version of variable, new line

On 2018-05-25 01:50, asa32s...@gmail.com wrote: hi just seeing if there is a cleaner way to write this. s1= "kitti" s2= 'kitti' i= 3 print(s1+ "\n" + "="*i + "^" + "\n" +s2) kitti ===^ kitti When printing, I'd probably just go for something clear and simple: print(s1) print("=" * i +

cleaner version of variable, new line

hi just seeing if there is a cleaner way to write this. s1= "kitti" s2= 'kitti' i= 3 print(s1+ "\n" + "="*i + "^" + "\n" +s2) > kitti ===^ kitti -- https://mail.python.org/mailman/listinfo/python-list

[issue27296] Urllib/Urlopen IncompleteRead with HTTP header with new line characters

rugk added the comment: Yeah, it might not be the standard or best practise to send such headers, but at least all mayor browsers and curl do not complain about this. Mayor browsers even threat this HPKP header as it is supposed. But instead of showing complex error messages Python could just

[issue27296] Urllib/Urlopen IncompleteRead with HTTP header with new line characters

Martin Panter added the comment: HTTP header fields are not supposed to have line breaks unless followed by a space or tab. So the server is actually providing a faulty response. However Python could do better at handling this case. There is already a bug open for this: Issue 24363. For the

[issue27296] Urllib/Urlopen IncompleteRead with HTTP header with new line characters

New submission from rugk: Test file: https://gist.github.com/rugk/3ea35d04d66c2295e02d0b6cb6d822a2 Python version: 2.7.5+ Issue description: When Urllib gets a HTTP header with line breaks/new line characters it shows the following error: ``` Traceback (most recent call last): File

[issue26503] argparse with required field , not having new line separator in -help dispaly

paul j3 added the comment: The usage line formatter needs a major rewrite. Currently it formats usage for all the arguments as one line (two actually, optionals and positionals are handled separately), and then breaks it into 'wrappable parts'. It then compiles the lines from these parts

[issue26503] argparse with required field , not having new line separator in -help dispaly

New submission from Mohankumar: We are using Python argsparse library here to display below --help message . In --help option , new line option not handled correctly , Especially in "mandatory parameters" (required=True) better to place a new line before for better readabili

New line conversion with Popen attached to a pty

with os.fdopen. I noticed that we kept getting a bunch of extra new line characters. This is all using python 2.6.4 in a centos6 environment. After some investigation I realised we needed to use universal_newline support so I enabled it for the Popen and specified the mode in the fdopen to be rU

Re: New line conversion with Popen attached to a pty

On Thursday, 20 June 2013 23:04:39 UTC+1, Peter Otten wrote: (2) Fiddle with terminal options, e. g. attrs = termios.tcgetattr(outSlave) attrs[1] = attrs[1] (~termios.ONLCR) | termios.ONLRET termios.tcsetattr(outSlave, termios.TCSANOW, attrs) p = subprocess.Popen(

Re: New line conversion with Popen attached to a pty

On Thursday, 20 June 2013 11:20:20 UTC+1, Jonathan Harden wrote: ...SNIP Sorry about the second post, it took a very long time to show up, long enough I thought it had been lost. -- http://mail.python.org/mailman/listinfo/python-list

Re: New line conversion with Popen attached to a pty

(pty) made with pty.openempty and opened with os.fdopen. I noticed that we kept getting a bunch of extra new line characters. Duplicate thread, delayed by the vagaries of email and gateways. In that thread, the problem has been happily resolved. Any responses, please keep them on the other

New line conversion with Popen attached to a pty

of output. To do this we have been attaching stdout from the subprocess.Popen to a pseudo terminal (pty) made with pty.openempty and opened with os.fdopen. I noticed that we kept getting a bunch of extra new line characters. This is all using python 2.6.4 in a centos6 environment. After some

Re: New line conversion with Popen attached to a pty

by the client program with each line of output. To do this we have been attaching stdout from the subprocess.Popen to a pseudo terminal (pty) made with pty.openempty and opened with os.fdopen. I noticed that we kept getting a bunch of extra new line characters. Mixing subprocess and explicit select

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Roundup Robot added the comment: New changeset 8b764c3521fa by Ezio Melotti in branch '2.7': #17714: document that the base64 codec adds a trailing newline. http://hg.python.org/cpython/rev/8b764c3521fa -- nosy: +python-dev ___ Python tracker

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Ezio Melotti added the comment: The str.encode() doc is the wrong place where to document this, since the '\n' is added only for the base64 codec. I added a note about this in the codecs docs[0]. [0]: http://docs.python.org/2/library/codecs.html#standard-encodings -- assignee:

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Roundup Robot added the comment: New changeset cbb23e40e0d7 by Ezio Melotti in branch '3.3': #17714: document that the base64 codec adds a trailing newline. http://hg.python.org/cpython/rev/cbb23e40e0d7 New changeset b3e1be1493a5 by Ezio Melotti in branch 'default': #17714: merge with 3.3.

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti stage: needs patch - patch review type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17714 ___

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Dmi Baranov added the comment: Added a patch -- keywords: +patch nosy: +dmi.baranov Added file: http://bugs.python.org/file30069/issue17714.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17714

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Changes by Terry J. Reedy tjre...@udel.edu: -- assignee: - docs@python components: +Documentation nosy: +docs@python stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17714

[issue17714] str.encode('base64') add trailing new line character is not documented

New submission from Alessandro Piccione: str.encode() with 'base64' as argument add a trailing new line character to the returned string. This is the difference from base64.b64encode(str) (that is used internally). This is not documented in str.encode() http://docs.python.org/2/library

[issue17714] str.encode('base64') add trailing new line character. It is not documented.

Changes by Alessandro Piccione alessandro.piccione...@gmail.com: -- title: str.encode('base64') add trailing new line character is not documented - str.encode('base64') add trailing new line character. It is not documented. ___ Python tracker rep

Replace dash values in a field with new line- VB equivalent of Python

Dear All, I need some assistance with Python so that values in the Name field e.g. Murray - James - Leo can be labeled as: Murray James Leo with a new line replacing every dash. Basically I need the equivalent of this VB in Python: replace ( [Name] , -, vbNewLine) I tried this but no luck

Re: Replace dash values in a field with new line- VB equivalent of Python

On Tue, Mar 19, 2013 at 11:36 AM, Cathy James nambo...@gmail.com wrote: Dear All, I need some assistance with Python so that values in the Name field e.g. Murray - James - Leo can be labeled as: Murray James Leo with a new line replacing every dash. Basically I need the equivalent

Re: Replace dash values in a field with new line- VB equivalent of Python

On 03/19/2013 11:36 AM, Cathy James wrote: Dear All, I need some assistance with Python so that values in the Name field e.g. Murray - James - Leo can be labeled as: Murray James Leo with a new line replacing every dash. Basically I need the equivalent of this VB in Python: replace ( [Name

Re: Replace dash values in a field with new line- VB equivalent of Python

On 2013-03-19, Cathy James nambo...@gmail.com wrote: Dear All, I need some assistance with Python so that values in the Name field e.g. Murray - James - Leo can be labeled as: Murray James Leo with a new line replacing every dash. Basically I need the equivalent of this VB in Python

Re: Replace dash values in a field with new line- VB equivalent of Python

On Mar 19, 8:36 pm, Cathy James nambo...@gmail.com wrote: Dear All, I need some assistance with Python so that values in the Name field e.g. Murray - James - Leo can be labeled as: Murray James Leo with a new line replacing every dash. Basically I need the equivalent of this VB

'subprocess.check_output' extra new line?

Hi I wonder if the additional new line charachter at the end of the standard output capture is on purpose with 'subprocess.check_output'? subprocess.check_output([ 'cygpath', 'C:\\' ]) '/cygdrive/c\n' If I do the same from the shell there is no extra new line (which is correct I believe

Re: 'subprocess.check_output' extra new line?

On Sat, Jan 5, 2013 at 2:50 AM, sbre...@hotmail.com wrote: Hi I wonder if the additional new line charachter at the end of the standard output capture is on purpose with 'subprocess.check_output'? subprocess.check_output([ 'cygpath', 'C:\\' ]) '/cygdrive/c\n' If I do the same from

RE: 'subprocess.check_output' extra new line?

03:14:46 +1100 Subject: Re: 'subprocess.check_output' extra new line? From: ros...@gmail.com To: python-list@python.org On Sat, Jan 5, 2013 at 2:50 AM, sbre...@hotmail.com wrote: Hi I wonder if the additional new line charachter at the end of the standard output capture is on purpose

[issue16087] How to open a csv file in universal new line mode?

New submission from Kason: I am trying to follow the tutorial at http://www.slideshare.net/niloyghosh1984/qgis-tutorial-1 and I got to slide 24 of 47 whereupon I tried to use the mmqgis plugin to open the csv file, but I got this error: Error: new-line character seen in unquoted field - do you

[issue16087] How to open a csv file in universal new line mode?

R. David Murray added the comment: The bug tracker isn't a good place to get help on using Python. You are more likely to find people to answer this sort of question on the python-list mailing list. If you are using python3, the answer is to use newline='', as discussed in the

[issue8086] ssl.get_server_certificate new line missing

Antoine Pitrou pit...@free.fr added the comment: This looks reasonable enough. -- nosy: +pitrou stage: unit test needed - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8086 ___

[issue8086] ssl.get_server_certificate new line missing

Antoine Pitrou pit...@free.fr added the comment: Fixed in r80557 (trunk) and r80558 (2.6). 3.1 and 3.2 weren't affected, but I still merged in the additional tests. Thank you! -- resolution: - fixed stage: patch review - committed/rejected status: open - closed

[issue8086] ssl.get_server_certificate new line missing

Changes by Kyle VanderBeek ky...@kylev.com: -- keywords: +patch Added file: http://bugs.python.org/file16672/python-ssl-PEM_FOOTER.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8086

[issue8086] ssl.get_server_certificate new line missing

Kyle VanderBeek ky...@kylev.com added the comment: Forgot to note that my patch is against 2.7 current trunk. -- nosy: +kylev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8086 ___

[issue8086] ssl.get_server_certificate new line missing

\n4VDGsFKbkmBLuCgnFaY+p4xvr2XL+bJmpm8+IQqW5Ob/OUSl7Vj4btHhF6VK29CI\n+DexDLRI0KqZ-END CERTIFICATE-\n' Notice no \n before -END CERTIFICATE-\n Platform: Linux x64 python 2.6.4 -- messages: 100595 nosy: offero severity: normal status: open title: ssl.get_server_certificate new line

[issue8086] ssl.get_server_certificate new line missing

Chris chris...@gmail.com added the comment: Did some more research and found this as the culprit: in Lib/ssl.py # ... def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None): ... return DER_cert_to_PEM_cert(dercert) def

[issue8086] ssl.get_server_certificate new line missing

R. David Murray rdmur...@bitdance.com added the comment: I think that's because encodestring tacks a 'courtesy newline' on to the end of the output it returns. textwrap.fill does't, and I'm guessing that's the code path that your installation is taking. -- components: +Library (Lib)

[issue8086] ssl.get_server_certificate new line missing

Changes by R. David Murray rdmur...@bitdance.com: -- versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8086 ___

[issue8086] ssl.get_server_certificate new line missing

Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +janssen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8086 ___ ___ Python-bugs-list

[issue5525] Problem with email.MIME* library, using wrong new line

R. David Murray rdmur...@bitdance.com added the comment: Effectively this is a duplicate of issue 1349106, since you are right that it affects more than just boundary production. I believe we are going to address this in a new version of the email module. -- nosy: +r.david.murray

[issue5525] Problem with email.MIME* library, using wrong new line

Luca clementi luca.cleme...@gmail.com added the comment: I forgot to say that the \n should be substitute with \r\n CRLF Luca -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5525 ___

[issue5525] Problem with email.MIME* library, using wrong new line

--' + boundary but if this function is run under Unix it print only the LF and not the CRLF as by required by the standard. My guess is that this error is also in other part of the library. SMTP (as HTTP) requires CRLF as new line, by standard, while I see that at the beginning of the generator.py NL = '\n

Re: wxpython - new line in radiobutton's label?

[EMAIL PROTECTED] wrote: I am creating a small gui using wxGlade and wxPython. I am using a radio button, and the text next to the options needs to be over two lines. I tried using a \n character, but it seems to get ignored. Looking around in the various wikis and the example code also

wxpython - new line in radiobutton's label?

Hi. I am creating a small gui using wxGlade and wxPython. I am using a radio button, and the text next to the options needs to be over two lines. I tried using a \n character, but it seems to get ignored. Looking around in the various wikis and the example code also didn't turn up anything.

Re: adding a new line of text in Tk

will be asking you some) I would actually like to add some text but it puts it all on one line.I would like to be able to tell it to start a new line. Just use \n in your string, e.g.: w = Label(root, text=Line 1\nLine 2\nLine 3) Or a triple-quoted string will do the trick: w

Re: adding a new line of text in Tk

) I would actually like to add some text but it puts it all on one line.I would like to be able to tell it to start a new line. Just use \n in your string, e.g.: w = Label(root, text=Line 1\nLine 2\nLine 3) Or a triple-quoted string will do the trick: w = Label(root, text=Line 1 Line 2 Line 3

interactive programme (add a new line in Tk)

somebody recently showed me how to create a new line using \n which was great.The thing is when i am creating the programme the text i wish to add is quite long.and it ends up stretching the width of several pages,which i think looks quite messy.Would it be possible for some one to show me how

Re: interactive programme (add a new line in Tk)

nigel wrote: somebody recently showed me how to create a new line using \n which was great.The thing is when i am creating the programme the text i wish to add is quite long.and it ends up stretching the width of several pages,which i think looks quite messy.Would it be possible for some

adding a new line of text in Tk

() root.mainloop() The problem i have is where i have started to write some textCongratulations you have made it this far,just a few more questions then i will be asking you some) I would actually like to add some text but it puts it all on one line.I would like to be able to tell it to start a new line

Re: how do you move to a new line in your text editor?

Which indenting features do you find missing? Note: 1.0.3 -- still unreleased -- has implemented if / elif /else auto unindent... Jorge Godoy wrote: Mc Osten [EMAIL PROTECTED] writes: Because I tried it and it just lacks a lot of functionality you get with TextMate or Emacs. It is quite

Re: how do you move to a new line in your text editor?

Fabio Zadrozny [EMAIL PROTECTED] writes: Which indenting features do you find missing? Note: 1.0.3 -- still unreleased -- has implemented if / elif /else auto unindent... The most basic one is not having my code moving forward with sucessive TABs pressed. When I press TAB on Emacs it use a

Re: how do you move to a new line in your text editor?

Ok, I'm putting those in my 'todo-list' ;-) -- keep an eye open for future releases... Cheers, Fabio Jorge Godoy wrote: Fabio Zadrozny [EMAIL PROTECTED] writes: Which indenting features do you find missing? Note: 1.0.3 -- still unreleased -- has implemented if / elif /else auto

Re: how do you move to a new line in your text editor?

John Salerno wrote: So I'm wondering, how do you all handle moving around in your code in cases like this? Is there some sort of consistency to these things that you can write rules for your text editor to know when to outdent? It doesn't seem like you can do this reliably, though. Under

Re: how do you move to a new line in your text editor?

John Salerno wrote: But I read in the PEP that spaces are recommended over tabs. If this is the case, it would involve pressing backspace 4 times (or 8, etc.) to get back to column 1. In the editor which I use, pressing the tab key indents the current line under the previous one the first

Re: how do you move to a new line in your text editor?

it easy to outdent when I need to start a new line in column 1. I can press backspace once and move 4 spaces to the left. But I read in the PEP that spaces are recommended over tabs. If this is the case, it would involve pressing backspace 4 times (or 8, etc.) to get back to column 1

Re: how do you move to a new line in your text editor?

On Thu, 02 Mar 2006 18:58:50 GMT, John Salerno wrote: I use UltraEdit right now, and it is possible to convert spaces and tabs back and forth, but it's just an extra step. I wouldn't definitely suggest UltraEdit to code Python. Probably you should try scite. I'm using TextMate (but it's

Re: how do you move to a new line in your text editor?

On Linux you can try out Scribes. It has a function to convert tabs to spaces. Personally, I use tabs in all my projects. http://scribes.sf.net/snippets.htm http://scribes.sf.net/ -- http://mail.python.org/mailman/listinfo/python-list

Re: how do you move to a new line in your text editor?

Mc Osten wrote: On Thu, 02 Mar 2006 18:58:50 GMT, John Salerno wrote: I use UltraEdit right now, and it is possible to convert spaces and tabs back and forth, but it's just an extra step. I wouldn't definitely suggest UltraEdit to code Python. Why do you say that? --

Re: how do you move to a new line in your text editor?

On Fri, 03 Mar 2006 16:48:11 GMT, John Salerno wrote: Why do you say that? Because I tried it and it just lacks a lot of functionality you get with TextMate or Emacs. It is quite stupid when indenting, just to name one. -- USB Priests for only 10$ --

Re: how do you move to a new line in your text editor?

it easy to outdent when I need to start a new line in column 1. I can press backspace once and move 4 spaces to the left. But I read in the PEP that spaces are recommended over tabs. If this is the case, it would involve pressing backspace 4 times (or 8, etc.) to get back to column 1. So I'm

Re: how do you move to a new line in your text editor?

Mc Osten [EMAIL PROTECTED] writes: Because I tried it and it just lacks a lot of functionality you get with TextMate or Emacs. It is quite stupid when indenting, just to name one. This is the main motive I don't use PyDev with Eclipse... It is a lot more stupid than python-mode on Emacs with

how do you move to a new line in your text editor?

to start a new line in column 1. I can press backspace once and move 4 spaces to the left. But I read in the PEP that spaces are recommended over tabs. If this is the case, it would involve pressing backspace 4 times (or 8, etc.) to get back to column 1. So I'm wondering, how do you all handle

Re: how do you move to a new line in your text editor?

to outdent when I need to start a new line in column 1. I can press backspace once and move 4 spaces to the left. But I read in the PEP that spaces are recommended over tabs. If this is the case, it would involve pressing backspace 4 times (or 8, etc.) to get back to column 1. So I'm wondering

Re: how do you move to a new line in your text editor?

John Salerno wrote: But I read in the PEP that spaces are recommended over tabs. If this is If you like tabs, stick with tabs. There isn't any reason to use spaces unless your boss is demanding it. Tabs are the slightly better choice, in my humble opinion. That said, you should be able to

Re: how do you move to a new line in your text editor?

John Salerno wrote: So I'm wondering, how do you all handle moving around in your code in cases like this? Is there some sort of consistency to these things that you can write rules for your text editor to know when to outdent? It doesn't seem like you can do this reliably, though. Emacs, at

Re: how do you move to a new line in your text editor?

Carl Banks wrote: John Salerno wrote: So I'm wondering, how do you all handle moving around in your code in cases like this? Is there some sort of consistency to these things that you can write rules for your text editor to know when to outdent? It doesn't seem like you can do this reliably,

Re: how do you move to a new line in your text editor?

John Salerno wrote: Carl Banks wrote: John Salerno wrote: So I'm wondering, how do you all handle moving around in your code in cases like this? Is there some sort of consistency to these things that you can write rules for your text editor to know when to outdent? It doesn't seem like

Re: how do you move to a new line in your text editor?

John Salerno wrote: I use UltraEdit right now, and it is possible to convert spaces and tabs back and forth, but it's just an extra step. I was thinking about trying vim, as I've heard it's easier to learn than emacs. Absolutely. It's also easier to learn to ride a Huffy than a Schwinn,

Re: how do you move to a new line in your text editor?

Carl Banks wrote: You wouldn't know if Ultraedit has some kind of hook mechanism (whereby it can execute a macro or script or something upon loading/saving). That could solve your problem. Obviously, having to manually convert isn't too helpful. I'll have to check on that. I know I can do

Re: how do you move to a new line in your text editor?

Paul McNett wrote: That said, you should be able to tell your editor how to behave in the indent/unindent case, no matter whether you use tabs or spaces. If not, time to switch editors! ;) I definitely can, I'm just a little unsure about what the special outdenting cases might be. The way

Re: how do you move to a new line in your text editor?

On Thu, 02 Mar 2006 18:39:55 GMT John Salerno [EMAIL PROTECTED] wrote: But I read in the PEP that spaces are recommended over tabs. If this is the case, it would involve pressing backspace 4 times (or 8, etc.) to get back to column 1. So I'm wondering, how do you all handle moving around

Re: how do you move to a new line in your text editor?

I use Vim, use spaces, and have no problems. It has a shorttabstop option, which causes backspace to backspace to the preceding multiple of tabwith spaces when the curser is after a set of spaces at the beginning of the line. It feels like I'm using tabs, but I'm not. In addition, within

  1   2   >