pretext-CLI-1.2.0 error

28 views
Skip to first unread message

Thomas Shemanske

unread,
Dec 18, 2022, 12:09:49 PM12/18/22
to PreTeXt development
I have taken the project I have been using for testing and tried today to produce html with pretext-CLI v 1.2.0.

The "pretext build web" command completes with no errors, but the "pretext build -g" produces the error below; full output from the pretext build -g command is attached.

Not sure what to make of it.

Tom

successful application of /home/trs/.ptx/xsl/pretext-html.xsl
critical: expected str, bytes or os.PathLike object, not NoneType
##################
Failed to build html.  Exiting...

----------------------------------------------------
While running pretext, the following errors occured:

critical: expected str, bytes or os.PathLike object, not NoneType
----------------------------------------------------
Exception ignored in atexit callback: <function exit_command at 0x7f635aa3eb00>
Traceback (most recent call last):
  File "/home/trs/.local/lib/python3.10/site-packages/pretext/utils.py", line 463, in exit_command
    sys.exit(1)
SystemExit: 1
pretext-output.txt

Oscar Levin

unread,
Dec 18, 2022, 1:10:00 PM12/18/22
to PreTeXt development
Hi Tom,

Could you try a couple things please?  First, if you run the same commands with 1.1.0, do you get a critical error?  You can reinstall 1.1 with `pip install pretext==1.1.0`.

Second, what output do you get around the error if you run in "debug" mode: pretext -v debug build -g.

I'm not sure why you are getting the traceback, but that is happening with the sys.exit(1) command, which hasn't been a problem.  The real error is the one reported as "critical", and I don't know if that is from the CLI or from core pretext.

Thomas R. Shemanske

unread,
Dec 18, 2022, 2:46:09 PM12/18/22
to prete...@googlegroups.com
Hi Oscar,

There are no errors with 1.1.0; I ran verbose debug with both versions.

Output is attached.

Tom

--
You received this message because you are subscribed to a topic in the Google Groups "PreTeXt development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/klKMunE1kAg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/6ada4472-6c40-4f4f-8a59-c8b7105bafden%40googlegroups.com.


--
Thomas R. Shemanske
Grantham, NH 

pretext-output-debug-verbose-1.1.0.txt
pretext-output-debug-verbose-1.2.0.txt

Rob Beezer

unread,
Dec 18, 2022, 3:10:04 PM12/18/22
to prete...@googlegroups.com
Recent CodeChat contribution. PathLib?

On 12/18/22 11:45, Thomas R. Shemanske wrote:
> Hi Oscar,
>
> There are no errors with 1.1.0; I ran verbose debug with both versions.
>
> Output is attached.
>
> Tom
>
> On Sun, Dec 18, 2022 at 1:10 PM Oscar Levin <oscar...@gmail.com
> <mailto:oscar...@gmail.com>> wrote:
>
> Hi Tom,
>
> Could you try a couple things please?  First, if you run the same commands
> with 1.1.0, do you get a critical error?  You can reinstall 1.1 with `pip
> install pretext==1.1.0`.
>
> Second, what output do you get around the error if you run in "debug" mode:
> pretext -v debug build -g.
>
> I'm not sure why you are getting the traceback, but that is happening with
> the sys.exit(1) command, which hasn't been a problem.  The real error is the
> one reported as "critical", and I don't know if that is from the CLI or from
> core pretext.
>
> On Sunday, December 18, 2022 at 10:09:49 AM UTC-7 thomas.r....@gmail.com
> <https://groups.google.com/d/topic/pretext-dev/klKMunE1kAg/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to
> pretext-dev...@googlegroups.com
> <mailto:pretext-dev...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pretext-dev/6ada4472-6c40-4f4f-8a59-c8b7105bafden%40googlegroups.com <https://groups.google.com/d/msgid/pretext-dev/6ada4472-6c40-4f4f-8a59-c8b7105bafden%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
>
>
> --
> Thomas R. Shemanske
> Grantham, NH
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-dev...@googlegroups.com
> <mailto:pretext-dev...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4iqAfBGJs5sUMeLUEbbzeFUpZDyv0w0jFsHBQVoFubTcw%40mail.gmail.com <https://groups.google.com/d/msgid/pretext-dev/CA%2Bz8C4iqAfBGJs5sUMeLUEbbzeFUpZDyv0w0jFsHBQVoFubTcw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Oscar Levin

unread,
Dec 18, 2022, 4:01:31 PM12/18/22
to PreTeXt development
Yup, that looks like the culprit.  I'll get a bugfix out in an hour or so.  Thanks Tom for the detailed report.  

Oscar Levin

unread,
Dec 18, 2022, 5:20:54 PM12/18/22
to PreTeXt development
Should be fixed if you `pip install pretext --upgrade` to get 1.2.1.  Please let me know if this doesn't fix the problem.

Thomas R. Shemanske

unread,
Dec 18, 2022, 5:25:07 PM12/18/22
to prete...@googlegroups.com
Success! Run `pretext view web` to see the results.

Thanks!

Tom

To unsubscribe from this topic, visit https://groups.google.com/d/topic/pretext-dev/klKMunE1kAg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pretext-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pretext-dev/e81b1372-a0f0-4376-bd3a-863b86ea546dn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages