I think it's best to post text directly or use something like a GitHub
Gist or a regular repository on GitHub.
It's hard to reason about things that aren't immediately visible in
the mailing list archive.
For example, one may want to add a comment to your code. It's
impossible with an attachment but it's
easy to do if there's some snippet in the previous email that can be quoted.
Here's an example:
> def hello(world):
The comment *here* would be that there's a typo in this line.
> return world
Also, if the source is really big, it's better to come up with a
minimal reproducer that would have way
fewer lines and rip off all the unrelated parts to help everyone focus
on important things.
пт, 20 груд. 2019 о 15:08 Jack Eisenbach <jackei...@gmail.com
> You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-user...@googlegroups.com
> To view this discussion on the web visit https://groups.google.com/d/msgid/cherrypy-users/76fec327-d637-41af-bf87-206a9cfe4ae3%40googlegroups.com
() ascii ribbon campaign - against html e-mail
- against proprietary attachments