On Monday, January 2, 2017 at 6:39:03 AM UTC-5, Antonio Caminero Garcia wrote:
> Hello, I am having a hard time deciding what IDE or IDE-like code editor
> should I use. This can be overwhelming.
>
> So far, I have used Vim, Sublime, Atom, Eclipse with PyDev, Pycharm, IntelliJ
> with Python plug
Use case:
===
1. OSX 10.7, bunch of .tex files culled from a blog via some cruddy old Perl
script.
.tex files are utf-8 encoded, which means the quotes and apostrophes drop out
going through pdflatex.
2. Recommend using git to manage the .tex files, which are all in a /src
directory in the p
On May 2, 11:29 pm, Ben Finney <[EMAIL PROTECTED]>
wrote:
> smitty1e <[EMAIL PROTECTED]> writes:
> > Just a fun exercise to unify some of the major input methods for a
> > script into a single dictionary.
> > Here is the output, given a gr.conf file in the sam
Just a fun exercise to unify some of the major input methods for a
script into a single dictionary.
Here is the output, given a gr.conf file in the same directory with
the contents stated below:
[EMAIL PROTECTED] ~/proj/mddl4/test $ ./inputs.py
{'source_db': '/home/sweet/home.db'}
[EMAIL PROTECTED
Since I haven't yet been shot for the earlier post of a .py to sqlite
rendering script, here is another script that takes the previous
output and does something useful.
Note that this is not the full integration with PyMacs--I rather hope
to spark some interest and save some time headbanging on a)
Disclaimer(s): the author is nobody's pythonista. This could probably
be done more elegantly.
The driver for the effort is to get PyMacs to work with new-style
classes.
This rendering stage stands alone, and might be used for other
purposes.
A subsequent post will show using the resulting file to
On Jun 10, 6:10 pm, John Machin <[EMAIL PROTECTED]> wrote:
> On Jun 11, 7:17 am, smitty1e <[EMAIL PROTECTED]> wrote:
>
> > The first print statement does what you'd expect.
> > The second print statement has rather a lot of rat in it.
> > The goal here is
The first print statement does what you'd expect.
The second print statement has rather a lot of rat in it.
The goal here is to write a function that will return the man page for
some command (mktemp used as a short example here) as text to client
code, where the groff markup will be chopped to ext
