CTCP ISSUE

Open
#242 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Locate the code at line 513, or line 518 in the GitHub file view, using the supplied image as a reference. Confirm the CTCP argument currently remains literally "{ctcptype}", apply the requested formatting change, and verify that the argument contains the actual CTCP type.

Written by the indexing model from the issue text.

Description

Please fix the issue on Line 513 (518 in the file on Github) by adding the "f" before the string format, or the CTCP will always have an argument of "{ctcptype}" (I mean literally that string.)

The image below shows where you may need to add a "f".

Image
Dominant language
Python
Stars
422
Forks
91
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/irc

All issues in jaraco/irc

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.