Trying to follow the instructions at https://github.com/roundup-tracker/roundup/blob/26224d88324b9bb9e394e7c3f2cb66e5dd03213d/doc/developers.txt#L117, I `hg clone`'d the repository and executed
ross@barley:/usr/local/src/roundup$ date; python3 ./demo -b sqlite
Sun 17 May 2026 11:13:48 PM PDT
python3: can't open file '/usr/local/src/roundup/./demo': [Errno 2] No such file or directory

I changed that to `./demo.py` and was able to start the program.

I think 2 things are missing from the instructions:

  1. Instructions to change to the project root directory.
  2. `.py` at the end of `./demo`.

Running Python 3.9 in a bash shell on Debian GNU/Linux 11 (old).

Hello Ross:

I fixed this in changeset:   8648:d2da5f9c2ea8.
Thanks for the report.

Just out of curiosity what led you to developers.txt rather than the directions
on the home page (https://www.roundup-tracker.org/#try-it-out) or in README.txt?

[I responded via email but the email bounced]

BTW, google stuck the bounce message in my spam folder, as it did with many messages from your site. I was unable to decode from the headers what they thought the problem was.

The bounce message, from roundup-admin, said
There was a problem with the message you sent:
   'ascii' codec can't decode byte 0xe2 in position 28: ordinal not in range(128)
I'm not exactly sure where to start count to get to 28 (headers? main body?), but the body begins (as rendered by google in the bounce mail)

On Mon, May 18, 2026 at 8:45=E2=80=AFAM John Rouillard
which certainly looks as if there are character coding issues.  When I view  the message I sent it looks completely ordinary.

>
> John Rouillard added the comment:
>
> Hello Ross:
>
> I fixed this in changeset:   8648:d2da5f9c2ea8.

Great!

> Thanks for the report.
>
> Just out of curiosity what led you to developers.txt rather than the dire
ctions
> on the home page (https://www.roundup-tracker.org/#try-it-out) or in READ
ME.txt?
>

I wanted  to get the source repository and how to run roundup from
there; I think it was the first spot I found that had the information, in particular the URL.

Hi Ross:

> BTW, google stuck the bounce message in my spam folder, as it did with many messages from
> your site. I was unable to decode from the headers what they thought the problem was.

I went a looked and have the same issue here. We have SPF defined, but no DKIM maybe that's 
the issue?

> The bounce message, from roundup-admin, said

Yeah, I did get your email on that.

> There was a problem with the message you sent:
>   'ascii' codec can't decode byte 0xe2 in position 28: ordinal not in range(128)
> I'm not exactly sure where to start count to get to 28 (headers? main body?), but the body
> begins (as rendered by google in the bounce mail)
>
>On Mon, May 18, 2026 at 8:45=E2=80=AFAM John Rouillard
>which certainly looks as if there are character coding issues.

The first = sign in the encoded line is at position 29, I don't remeber offhand if the
"position" is 0 or 1 based. I wonder what char is there in the original message. Maybe a
non-breaking space or something?

In any case the tracker is running roundup 1.6 ish under python 2. We are
a guest on the system and can't upgrade at the moment. There were a number of bugs
in encoding in 1.6 and python2.

> I fixed this in changeset:   8648:d2da5f9c2ea8.

There was a delay in pushing the changes upstream. Sourceforge was having issues.
So you might not have seen the changes for a bit.

> I wanted  to get the source repository and how to run roundup from there;
> I think it was the first spot I found that had the information, in particular the URL.

Got it. Well thanks for being an early beta tester for 2.6 8-).

-- rouilj