Fixed "print function's "end" option error in CPython"

[Sungmin-Joo]

The following code writes different string to the stream than in CPython:

print(1,2,3, end="||\n")

I fixed that bug by modifying the code
resolved: #93

[codecov-io]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.10%. Comparing base (e427daf) to head (0d6c264).

Additional details and impacted files

@@ Coverage Diff @@## master #92 +/- ##
==========================================
+ Coverage 69.09% 69.10% +0.01% 
==========================================
Files 60 60 Lines 10674 10678 +4 ==========================================
+ Hits 7375 7379 +4 
Misses 2781 2781 Partials 518 518 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[corona10]

@Sungmin-Joo Please add a unit test which you updated.

[Sungmin-Joo]

@corona10
Is it a proper test?
If not, I will try again tomorrow.

[corona10]

@Sungmin-Joo
You should show the test

AS-IS

>>>print(1,2,3, end="||\n")
1||2||3||

TO-BE

>>>print(1,2,3, end="||\n")
123||

[corona10]

The test is not proper.

[sbinet]

what about:

switchsep, ok:=kwargs["sep"]; ok {
casetrue:
sepObj=sepdefault:
sepObj=py.String(" ")
}

[sbinet]

Suggested change

	assertok, "TypeError not raised"
	assertok, "TypeError not raised when 'sep' is not in the kwargs dict"

that said, I am not sure I understand this test.
do we really want this line to raise an exception? why?

[sbinet]

Suggested change

	print("hello","gpython", end="123\n")
	print("hello","gpython", end="123\n")

[corona10]

@Sungmin-Joo@sbinet
Sorry,
I think that we should fix #90 was not the proper approach.

err:=py.ParseTupleAndKeywords(nil, kwargs, "|ssOO:print", kwlist, &sepObj, &endObj, &file, &flush)

I am now closing this PR
Let's fix this issue with proper approach :)