[issue45020] Freeze all modules imported during startup.

2021-10-01 Thread santhosh


Change by santhosh :


--
components: +Parser -Build
nosy: +lys.nikolaou, pablogsal, santhu_reddy12
versions: +Python 3.9 -Python 3.11

___
Python tracker 
<https://bugs.python.org/issue45020>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue44999] Argparse missing translates

2021-08-25 Thread santhosh


New submission from santhosh :

Dear all,

There are a few strings in the `argparse` module which are not translatable 
through the `gettext` API.

Some have already been reported:
- the "--version" help text at Lib/argparse.py:1105 (reported in issue 16786, 
fixed by PR 12711);
- the "default" help text at Lib/argparse.py:697 (reported in 33775, fixed by 
PR 12711).

However, some others remain:
- the "default" help text for `BooleanOptionalAction` at Lib/argparse.py:878 
(which, incidentally, will be duplicated when used with 
`ArgumentDefaultsHelpFormatter`);
- the "argument %(argument_name)s: %(message)s" error message at 
Lib/argparse.py:751;
- the formatted section heading at Lib/argparse.py:225: if the heading itself 
is translatable, the string "%(heading)s:" is not. More precisely, the colon 
right after the heading might also require localization, as some languages 
(e.g., French) typeset colons with a preceding non-breaking space (i.e., 
"%(heading)s :"). (Okay, I'll admit that this is nitpicking!)

I'll submit a pull request with proposed fixes for these strings.

Kind regards,
Santhosh

--
components: Parser
messages: 400251
nosy: lys.nikolaou, pablogsal, santhu_reddy12
priority: normal
severity: normal
status: open
title: Argparse missing translates
type: performance
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue44999>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41322] unittest: deprecate test methods returning non-None values

2021-08-19 Thread santhosh


Change by santhosh :


--
nosy: +fdrake, stefan, terry.reedy
versions: +Python 3.7 -Python 3.8

___
Python tracker 
<https://bugs.python.org/issue41322>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41322] unittest: deprecate test methods returning non-None values

2021-08-19 Thread santhosh


santhosh  added the comment:

def split_module_names(module):
unnamed, named = set(), set()
for name in dir(module):
if not name.startswith('_'):
attr = getattr(module, name)
try:
if hasattr(attr, '__name__'):
named.add(name)
else:
unnamed.add(name)
except TypeError:
pass
return named, unnamed

--
nosy: +santhu_reddy12 -andrei.avk, defreng, ezio.melotti, lukasz.langa, 
michael.foord, rbcollins, serhiy.storchaka, terry.reedy, xtreak, zach.ware
versions: +Python 3.8 -Python 3.11

___
Python tracker 
<https://bugs.python.org/issue41322>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue33063] failed to build _ctypes: undefined reference to `ffi_closure_FASTCALL'

2021-07-23 Thread santhosh


santhosh  added the comment:

build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 In function `ffi_prep_closure_loc':
/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.c:678: undefined 
reference to `ffi_closure_FASTCALL'
/usr/bin/ld: 
build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 relocation R_386_GOTOFF against undefined hidden symbol `ffi_closure_ 
FASTCALL' can not be used when making a shared object
/usr/bin/ld: final link failed
build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 In function `ffi_prep_closure_loc':
/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.c:678: undefined 
reference to `ffi_closure_FASTCALL'
/usr/bin/ld: 
build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/c//c/types/li bf 
fi/ s 
rc/x86/ffi.o: relocation R_386_GOTOFF against undefined hidden symbol `ffi_ 
closure_ FAST CALL' can not be used when making a shared object
/usr/bin/ld: final link 
failedbuild/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 In function `ffi_prep_closure_loc':
/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.c:678: undefined 
reference to `ffi_closure_FASTCALL'
/usr/bin/ld: 
build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 relocation R_386_GOTOFF against undefined hidden symbol `ffi_closure_FASTCALL' 
can not be used when making a shared object
/usr/bin/ld: final link 
failedbuild/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffio:
 In function `ffiprep_closure_loc':
/opt/python/Python-3.5.5/Modules/_ c types/ b f fi/sr c/x86/ffi.c:678: 
undefined reference to ` ff_ closure_ FAST CALL'
/usr/bin/ld: 
build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 relocation R_386_GOTOFF against undefined hidden symbol `ffi_closure_FASTCALL' 
can not be used when making a shared object
/usr/bin/ld: final link 
failedbuild/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 In function `ffi_prep_closure_loc':
/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.c:678: undefined 
reference to `ffi_closure_FASTCALL'
/usr/bin/ld: 
build/temp.linux-x86_64-3.5/opt/python/Python-3.5.5/Modules/_ctypes/libffi/src/x86/ffi.o:
 relocation R_386_GOTOFF against undefined hidden symbol `ffi_closure_FASTCALL' 
can not be used when making a shared object
/usr/bin/ld: final link failed

--
nosy: +santhu_reddy12

___
Python tracker 
<https://bugs.python.org/issue33063>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22994] datetime buggy

2014-12-05 Thread santhosh

santhosh added the comment:

Thanks simeon.visser,
I understood your point. Didn't got your point earlier.

Hey belopolsky,
Here is the solution
val=datetime.datetime.strptime(2015-02-01,'%Y-%m-%d').date()
zon=pytz.timezone('US/Pacific')

Bad Code:
dt=datetime.datetime(val.year,val.month,val.day, tzinfo=zon)
Good Code:
dt=zon.localize(datetime.datetime(val.year,val.month,val.day))

In Linux, good code works perfectly

Both code are working perfectly in Mac

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22994
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22994] datetime buggy

2014-12-04 Thread santhosh

New submission from santhosh:

val=datetime.datetime.strptime(2015-02-01,'%Y-%m-%d').date()
zon=pytz.timezone('US/Pacific')
dt=datetime.datetime(val.year,val.month,val.day, tzinfo=zon)
print dt,zon


output:
2015-02-01 00:00:00-07:53 US/Pacific

output should be
2015-02-01 00:00:00-08:00 US/Pacific

--
messages: 232119
nosy: santhoshch
priority: normal
severity: normal
status: open
title: datetime buggy
type: behavior
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22994
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22994] datetime buggy

2014-12-04 Thread santhosh

santhosh added the comment:

i dont need local timezone
i need other timezones like: (US/Pacific)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22994
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22994] datetime buggy

2014-12-04 Thread santhosh

santhosh added the comment:

zon=pytz.timezone('America/New_York')
dt=datetime.datetime(2014,02,01, tzinfo=zon)
print dt,zon

= 2015-02-01 00:00:00-04:56 America/New_York

zon=pytz.timezone('Asia/Kolkata')
dt=datetime.datetime(2014,02,01, tzinfo=zon)
print dt,zon

=2015-02-01 00:00:00+05:53 Asia/Kolkata

all most for all timezones it is giving erroronous outputs
we are dealing many timezones

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22994
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue6895] locale._parse_localename fails when localename does not contain encoding information

2010-02-13 Thread Santhosh Thottingal

Santhosh Thottingal santhosh.thottin...@gmail.com added the comment:

I see that the ml_IN added to locale.alias of X.org. 
lemburg, Do you think that my patch is still required as a fallback solution in 
case xx_YY mapping not found in locale.alias? 
If you can confirm that it is not required, we can close this bug.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6895
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue6895] locale._parse_localename fails when localename does not contain encoding information

2009-09-17 Thread Santhosh Thottingal

Santhosh Thottingal santhosh.thottin...@gmail.com added the comment:

Attached the testcases as a patch to Lib/test/test_locale.py

--
Added file: http://bugs.python.org/file14915/test_locale.py.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6895
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue6895] locale._parse_localename fails when localename does not contain encoding information

2009-09-12 Thread Santhosh Thottingal

New submission from Santhosh Thottingal santhosh.thottin...@gmail.com:

locale._parse_localename fails when the locale name is in xx_YY format.
For example when the system locale is Malayalam(India),  ml_IN we get
the following result
 locale._parse_localename(ml_IN)
Traceback (most recent call last):
  File stdin, line 1, in module
  File /opt/python311/lib/python3.1/locale.py, line 424, in
_parse_localename
raise ValueError('unknown locale: %s' % localename)
ValueError: unknown locale: ml_IN
The expected result is ('ml_IN', None)
For Latin languages, locale.py assumes iso-8859-15 as the encoding type
if encoding type is not given in localename. In case 
of other locales, None can be returned for encoding type.
Attached patch fixes this.
The result after applying patch to locale.py
 import locale
 locale._parse_localename(ml_IN)
('ml_IN', None)

--
components: Library (Lib)
files: locale.py-parselocale-patch.diff
keywords: patch
messages: 92546
nosy: santhosh.thottingal
severity: normal
status: open
title: locale._parse_localename fails when localename does not contain encoding 
information
type: crash
versions: Python 3.1
Added file: http://bugs.python.org/file14881/locale.py-parselocale-patch.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6895
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com