Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #67145

Re: posting code snippets

Show key headers only | View raw

On Thu, Feb 27, 2014 at 7:13 AM, Mark H. Harris <harrismh777@gmail.com> wrote:
> hi folks,
>    Its been too long... can't remember... are there rules here about posting code snippets, or length considerations, and so forth?

Chris' advice about just posting your code inline with your message is
good.  If the problem is that you think your code is too long to post
inline, you're probably right.  That means it's probably also too long
for people to give it much attention.  If you really want people to
help figure out what is going on with code you don't understand, the
best thing to do is to post a Short, Self Contained, Correct Example
(http://www.sscce.org/).  That means cutting the code down to the bare
minimum required to demonstrate your issue.  Many times, the very act
of cutting the code down to a digestible chunk will show you the
problem without posting.  And if you still don't understand what's
going on, you're much more likely to get help when you present a
problem that can be read in a single screenful or so of code.

>    A related question, is there a python repository for uploading  py  files, patches, suggestions, etc?

Assuming this goes beyond posting code for people on the list to look
at, yes, there are lots of places to post python code.

For short bits, Activestate has a repository of python recipes:
http://code.activestate.com/recipes/langs/python/

For publishing full modules and packages, there's the python package
index: https://pypi.python.org/pypi

Patches, bugs and feature requests for the python language itself
belong here: http://bugs.python.org/ attached to an appropriate
tracker issue.  Feature requests should probably be raised on the
python-ideas mailing list
(https://mail.python.org/mailman/listinfo/python-ideas) before opening
an issue on the bug tracker.

-- 
Jerry

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

posting code snippets "Mark H. Harris" <harrismh777@gmail.com> - 2014-02-27 04:13 -0800
  Re: posting code snippets Chris Angelico <rosuav@gmail.com> - 2014-02-27 23:27 +1100
  Re: posting code snippets Jerry Hill <malaclypse2@gmail.com> - 2014-02-27 10:01 -0500
    Re: posting code snippets "Mark H. Harris" <harrismh777@gmail.com> - 2014-02-27 07:23 -0800
  Re: posting code snippets Tim Chase <python.list@tim.thechases.com> - 2014-02-27 09:56 -0600
  Re: posting code snippets Ben Finney <ben+python@benfinney.id.au> - 2014-02-28 09:15 +1100
    Re: posting code snippets "Mark H. Harris" <harrismh777@gmail.com> - 2014-02-27 15:13 -0800
      Re: posting code snippets Dave Angel <davea@davea.name> - 2014-02-28 00:05 -0500
  Re: posting code snippets Chris Angelico <rosuav@gmail.com> - 2014-02-28 16:41 +1100
    Re: posting code snippets Grant Edwards <invalid@invalid.invalid> - 2014-02-28 14:31 +0000
      Re: posting code snippets Gene Heskett <gheskett@wdtv.com> - 2014-03-01 16:55 -0500
      Re: posting code snippets Chris Angelico <rosuav@gmail.com> - 2014-03-02 09:16 +1100
        Re: posting code snippets Alister <alister.ware@ntlworld.com> - 2014-03-02 11:25 +0000
          Re: posting code snippets Gene Heskett <gheskett@wdtv.com> - 2014-03-02 07:20 -0500
      Re: posting code snippets Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-03-02 17:20 +1300

csiph-web