[issue45971] calendar module issue

Christian Heimes added the comment: > Note: Sep. 1752 had only 19 days. ( 11 days skipped ) That statement is only correct for countries where the Church of England was predominant: Great Britain and colonies of the British Empire in e.g, North America (later known as US of A). Alaska

[issue45971] calendar module issue

Vedran Čačić added the comment: https://docs.python.org/3/library/calendar.html#module-calendar The functions and classes defined in this module use an idealized calendar, the current Gregorian calendar extended indefinitely in both directions.

[issue45971] calendar module issue

5 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Note: Sep. 1752 had only 19 days. ( 11 days skipped ) -- components: Extension Modules messages: 407567 nosy: ssv5088 priority: normal severity: normal status: open title: calendar module issue versions: Python 3.8 __

Re: Module Issue

Abdur-Rahmaan Janhangeer writes: > i have a project at > > https://github.com/Abdur-rahmaanJ/honeybot > > see https://github.com/Abdur-rahmaanJ/honeybot/tree/master/honeybot > > my question is : > > how to include a util file / module that can be imported in both >

Module Issue

i have a project at https://github.com/Abdur-rahmaanJ/honeybot see https://github.com/Abdur-rahmaanJ/honeybot/tree/master/honeybot my question is : how to include a util file / module that can be imported in both core_plugins and user_plugins? if that is too difficult, let us take only

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Changes by Berker Peksag : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

Python STEP file color and module issue.

In the latest version of pythonOCC-0.16.0-win32-py34 its supporting WEBGGL that's a great one but its showing only one color and also its does not have all the module when I am going to compare this pythonOCC-0.16.0-win32-py34 with pythonOCC-0.4.win32-py2.6. So my questions are - 1) How to get

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Roundup Robot added the comment: New changeset be3b4aa2ad28 by doko in branch '2.7': - Issue #13150, #17512: sysconfig no longer parses the Makefile and config.h http://hg.python.org/cpython/rev/be3b4aa2ad28 -- nosy: +python-dev ___ Python tracker

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Benjamin Peterson added the comment: Can landed corrected in 2.7.5. -- priority: release blocker - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Matthias Klose added the comment: tested the backport on MacOSX, fixing the build. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___ ___

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Changes by Ned Deily n...@acm.org: -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___ ___ Python-bugs-list mailing list

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Ronald Oussoren added the comment: Reverting the backport would also fix the breakage. Is the addition of _sysconfigdata not a new feature? It changes the place where sysconfig (and distutils sysconfig?) looks for configuration data, and hence breaks all instructions that mention that you can

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Ronald Oussoren added the comment: Guess what, I hadn't read the thread on this python-dev yet :-( -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Benjamin Peterson added the comment: I backed it out until it can be done without breaking OSX. d174cb3f5b9e -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

? -- assignee: doko components: Build messages: 184919 nosy: benjamin.peterson, doko, ronaldoussoren priority: release blocker severity: normal stage: needs patch status: open title: backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin versions: Python 2.7

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Matthias Klose added the comment: untested work-around. we don't need the builddir to generate the _sysconfigdata.py. -- keywords: +patch Added file: http://bugs.python.org/file29537/workaround.diff ___ Python tracker rep...@bugs.python.org

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Changes by Matthias Klose d...@debian.org: -- nosy: +pitrou, twouters ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___ ___ Python-bugs-list

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Benjamin Peterson added the comment: Backporting 4742e7aea2f5 would seem to be the simplest and most correct solution. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17512 ___

[issue17512] backport of the _sysconfigdata.py module (issue 13150) breaks the build on darwin

Matthias Klose added the comment: here's the backport, tested on Linux only. sorry, can't test this on MacOSX before Sunday. -- Added file: http://bugs.python.org/file29543/backport.diff ___ Python tracker rep...@bugs.python.org

Re: deprecated string module issue

On Jun 25, 11:14 pm, Steven D'Aprano st...@remove-this- cybersource.com.au wrote: On Fri, 25 Jun 2010 16:31:17 -0500, GrayShark wrote: Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? I see only one person

Re: deprecated string module issue

On 6/26/10 3:56 AM, John Pinner wrote: On Jun 25, 11:14 pm, Steven D'Apranost...@remove-this- cybersource.com.au wrote: Terry made the very reasonable observation that you would serve the community, and thank us, by posting a bug report to pylint, rather than just ignoring it, and you respond

Re: deprecated string module issue

On Fri, 25 Jun 2010 01:29:22 +, Benjamin Peterson wrote: GrayShark howe.steven at gmail.com writes: Sorry, I meant from string import lowercase, uppercase Technically, you should use ascii_lowercase and ascii_uppercase, though I don't know if that's the cause of pylint's complaints.

Re: deprecated string module issue

On Fri, Jun 25, 2010 at 7:02 AM, GrayShark howe.ste...@gmail.com wrote: Thanks for the suggestion. I gave it a quick try. Same 'warning'. No, using the string module is the issue. Perhaps I'll just ignore it. Perhaps? Why perhaps? The warning is simply factually wrong-- therefore, there's no

Re: deprecated string module issue

On 6/25/2010 10:02 AM, GrayShark wrote: Thanks for the suggestion. I gave it a quick try. Same 'warning'. No, using the string module is the issue. Perhaps I'll just ignore it. And what about the next naive user of pylint? Submitting a bug report to the author of pylint would take much less

Re: deprecated string module issue

Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? As to your comment about Logilab's pylint. I'v seen a ticket similar to this from three months back. I assume they're not fixing it because if you review

Re: deprecated string module issue

On Fri, 25 Jun 2010 16:31:17 -0500, GrayShark wrote: Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? I see only one person being rude here, and that's you. Terry made the very reasonable observation that you

Re: deprecated string module issue

First up please don't top post. Second (although I'm sure Terry Reedy can speak for himself) said TJR has put more into Python than I've drunk pints of beer, and that's saying something, so you accusing him of being rude to me stinks!!! Please apologise or get off of this ng/ml. Disgusted.

Re: deprecated string module issue

Uhh... On Fri, Jun 25, 2010 at 2:31 PM, GrayShark howe.ste...@gmail.com wrote: As to your comment about Logilab's pylint. I'v seen a ticket similar to this from three months back. I assume they're not fixing it because if you review 'string' via pydoc you'd read this:

Re: deprecated string module issue

On 6/25/10 4:31 PM, GrayShark wrote: Why the rudness Terry Jan Reedy? Get up on the wrong side of the bed? Or worse luck, no one on the other side to create a wrong side? As to your comment about Logilab's pylint. I'v seen a ticket similar to this from three months back. I assume they're not

deprecated string module issue

In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string functions are now in _builtin_. Where are the constants? Thanks Steven --

Re: deprecated string module issue

On Thu, Jun 24, 2010 at 10:06 AM, GrayShark howe.ste...@gmail.com wrote: In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string functions are now in _builtin_.

Re: deprecated string module issue

On Jun 24, 10:06 am, GrayShark howe.ste...@gmail.com wrote: In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string functions are now in _builtin_. Where are

Re: deprecated string module issue

On Thu, Jun 24, 2010 at 10:39 AM, GrayShark howe.ste...@gmail.com wrote: Sorry, I meant from string import lowercase, uppercase As I was joining these two, I just changed the import to 'letters' So if the constants are not deprecated, why is the module? Is some other state then deprecated

Re: deprecated string module issue

On 06/24/2010 07:39 PM, GrayShark wrote: On Jun 24, 10:06 am, GrayShark howe.ste...@gmail.com wrote: In my code I have: from string import lower, upper When I use pylint on the program I get just one warning: Uses of a deprecated module 'string'. Iv'e noted that many if not all string

Re: deprecated string module issue

On 6/24/2010 1:50 PM, Ixokai wrote: On Thu, Jun 24, 2010 at 10:39 AM, GrayShark howe.ste...@gmail.com So if the constants are not deprecated, why is the module? Is some Again: the string module is not deprecated. It simply is not. GrayShark, pylint has a bug. Tell the author that its

Re: deprecated string module issue

GrayShark howe.steven at gmail.com writes: Sorry, I meant from string import lowercase, uppercase Technically, you should use ascii_lowercase and ascii_uppercase, though I don't know if that's the cause of pylint's complaints. -- http://mail.python.org/mailman/listinfo/python-list

Re: Tar module issue

Thx for your response. The fact is that I use tar.close() at the end of my code. This is really a random behaviour cause with an archive which has a short directory tree, I don't have this kind of beahavior and the archive works. thx On Mon, 2005-02-07 at 13:01 +, Russell Bungay wrote: