`__new__` ignores all arguments

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, python
Domain
compilers

Research direction

Start by reproducing the example through the new entry point with transcrypt test.py --nomin, and inspect the generated JavaScript for how constructor arguments are handled. Done means the arguments in __new__(Date, (2024, 8, 25)) are passed on to the JavaScript Date construction.

Written by the indexing model from the issue text.

Description

IS: bug?

When constructing JavaScript objects using __new__ the arguments aren't passed on to JS. For example,

new_date = __new__(Date, (2024, 8, 25))

compiles to

// [boilerplate]
export var new_date = new Date;

Used command: transcrypt test.py --nomin
Transcrypt version: 3.9.3

Dominant language
Python
Stars
2.9k
Forks
218
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 TranscryptOrg/Transcrypt

All issues in TranscryptOrg/Transcrypt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.