[issue5010] repoened "test_maxint64 fails on 32-bit systems due to assumption that 64-bit fits into "long"" due to it being closed without asking me whether there was anything else involved

2009-01-20 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : this is reopening http://bugs.python.org/issue4977 because it was closed without asking whether there was any further information or anything else that required investigation. there is no way for me to reopen the bug so i am forced to open a

[issue4977] test_maxint64 fails on 32-bit systems due to assumption that 64-bit fits into "long"

2009-01-20 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: hiya folks, lots of comments here. in no particular order: 1) thanks for reopening the bug 2) apologies for not being clearer - it's Lib/test/test_testzip.py specifically the TestZip64InSmallFiles case that's failing. 3) it's

[issue4954] native build of python win32 using msys under wine.

2009-01-21 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: updated. incorporating roumen's work as well. Added file: http://bugs.python.org/file12826/f ___ Python tracker <http://bugs.python.org/i

[issue5026] [reopening] native build of python win32 using msys under wine.

2009-01-21 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : reopening a new bug with the exact same title due to #4954 having been unilaterally closed without discussion, nor reasons specified. simple courtesy would dictate that some sort of dialog is entered into especially when someone is putting in

[issue5026] [reopening] native build of python win32 using msys under both wine and native win32

2009-01-21 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: so. let me be clear. this bug is a continuation of work to port python to mingw, with a specific BUT NOT UNIQUE focus of ensuring that python can be compiled under wine. THE ATTACHED PATCH CAN ALSO BE USED TO COMPILE PYTHON UNDER WIN32

[issue5026] [reopening] native build of python win32 using msys under both wine and native win32

2009-01-21 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: attached also manifests and rc files for building on msvcr80 Added file: http://bugs.python.org/file12829/x ___ Python tracker <http://bugs.python.org/issue5

[issue4954] native build of python win32 using msys under wine.

2009-01-21 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: manifests and rc files for msvcr80 build Added file: http://bugs.python.org/file12830/x ___ Python tracker <http://bugs.python.org/issue4

[issue4954] native build of python win32 using msys under wine.

2009-01-21 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: martin, so sorry, i didn't see your comments - no dang hell no i'm not done yet. regarding graminit.h: graminit.h isn't being removed - i keep editing it out of the patch. i'm not _submitting_ it as part of the patch because

[issue5026] [reopening] native build of python win32 using msys under both wine and native win32

2009-01-21 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: martin - apologies for shouting: i hadn't seen your explanations of why #4954 was closed. i'm not happy that it _was_ closed, but that's another story. yes of course i will be going on to python2.6 and up - first though is to foc

[issue5043] get_msvcr() returns None rather than []

2009-01-24 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : def get_msvcr(): """Include the appropriate MSVC runtime library if Python was built with MSVC 7.0 or later. """ msc_pos = sys.version.find('MSC v.') if msc_pos != -1: ms

[issue5046] native win32 and wine mingw+msys build of python2.7

2009-01-24 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : this is an update of the mingw+msys port for native win32, with the aim of being both compiled and used under both wine-win32 and native-win32. it is not a cross-compile patch. it does not require -lwine. it does not require a unix system. it

[issue5026] [reopening] native build of python win32 using msys under both wine and native win32

2009-01-24 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: #5046 supercedes this patch, for python2.7. still relevant for python2.5 though. ___ Python tracker <http://bugs.python.org/issue5

[issue5051] test_update2 in test_os.py invalid due to os.environ.clear() followed by reliance on environ COMSPEC

2009-01-25 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : class EnvironTests(mapping_tests.BasicTestMappingProtocol): """check that os.environ object conform to mapping protocol""" type2test = None def _reference(self): return {"KEY1":&

[issue5056] PyAPI assumes OS can access shared data in loadable modules (windows can't)

2009-01-25 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : an assumption has been made in the python core api that all operating systems "dynamic module loading" can access data segments. windows _cannot_ do this. the "workaround" has been to statically link absolutely _every

[issue5058] stop pgen.exe from generating CRLF-ended files and causing mayhem with win32-based patch submissions

2009-01-25 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : diff --git a/Parser/pgenmain.c b/Parser/pgenmain.c index fc27a2c..a4d4911 100644 --- a/Parser/pgenmain.c +++ b/Parser/pgenmain.c @@ -49,7 +49,7 @@ main(int argc, char **argv) graminit_h = argv[2]; graminit_c = argv[3]; g

[issue5056] PyAPI assumes OS can access shared data in loadable modules (windows can't)

2009-01-25 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: apologies - case of mistaken identity! patch attached - beginnings of moving data over to accessor-functions. attached here because it is relevant for "vector-table" future work. please close this bug. -- keywords: +patch

[issue3871] cross and native build of python for mingw32 with distutils

2009-02-03 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: On Mon, Feb 2, 2009 at 9:10 PM, Roumen Petrov wrote: > > Roumen Petrov added the comment: > > The proposed patch for this issue include parts of other pending issues > - so its all is single file. If python team don't like i

[issue34428] tokenize

2018-08-18 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : https://github.com/hhatto/autopep8/issues/414 the following two lines of code are not parseable by tokenize.py: co = re.compile( "\(") the combination of: * being split on two lines * having a backslash inside quotes

[issue34428] tokenize

2018-08-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: these two line also pass (do not throw an exception): co = re.compile( r"\(") the code that fails may be further reduced to the following: ( "\(") -- ___ Py

[issue34428] tokenize

2018-08-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: python2.7 and 3.5 also has exact same issue. -- versions: +Python 2.7, Python 3.5 ___ Python tracker <https://bugs.python.org/issue34

[issue34428] tokenize

2018-08-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: regular expressions are not something i am familiar or comfortable with (never have been: the patterns are too dense). however REMOVING "Bracket" from the regular expression(s) for PseudoToken "fixes" the problem. some de

[issue34428] tokenize

2018-08-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: wtf??? neither can i import io import tokenize text = r'''\ ( r"\(") ( "\(") ''' string_io = io.StringIO(text) tokens = list( tokenize.generate_tokens(string_io.readline) ) print (

[issue34428] tokenize

2018-08-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: ahh darn-it, autopep8 is passing in tokens line-by-line, to be parsed one at a time oh and of course it's losing state information that tokenizer critically relies on. i *think* that's what's going on so it's hig

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

2018-08-21 Thread Luke Kenneth Casson Leighton
New submission from Luke Kenneth Casson Leighton : adding some unit tests to some code being written, searched randomly on the internet for an IPv6 test suite and found one in php *shudder* # https://github.com/gws/ipv6-address-test/blob/master/Tests/Ipv6TestCase.php converted it to python

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

2018-08-22 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: > Hi lkcl, are you working on the fix? I'd like to work on it. hi prudvi, i'm not: i'm simply making people aware that there's an issue that needs to be addressed (pun intended) -- ___

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

2018-08-24 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: hi prudvi: i have absolutely no idea. i am simply running test validators online, which show and confirm that they are correctly INVALID. a google search shows a number of IPv6 validators: https://www.google.co.uk/search?q=ipv6+address

[issue34428] tokenize

2018-08-25 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: yep good call terry, not getting any response from the autopep8 developer, and i believe it was down to a loop where the text is being thrown line-by-line at tokenize and it was losing critical state information. so... not a bug in tokenize

[issue34453] ipaddress module accepts some strange IPv6 addresses that it shouldn't

2018-08-25 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: that's interesting, michael: it means that all of the IPv6 validators online are wrong, like this one! https://formvalidation.io/guide/validators/ip/ -- ___ Python tracker <https://bugs.py

[issue3871] cross and native build of python for mingw32 with packaging

2012-06-30 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: > distutils2 is the place to add such new features. you're not getting it. you've just told both this mingw32 project and also the new effort by ray that they can go fuck themselves, because their efforts are a total waste of ti

[issue3871] cross and native build of python for mingw32 with packaging

2012-06-30 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: > The feature freeze applies to all branches. Even when 3.4 starts, the > same rule that has been repeatedly explained for two years will apply: > no new features in distutils. Again, neither Tarek nor I are happy > about that, bu

[issue3871] cross and native build of python for mingw* hosts

2013-01-26 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: the last time this was brought up on python-dev the opinions of the primary python developers was made very very clear: anything that is not written by them is treated with extreme hostile and predudicial contempt. what i mean by that is that

[issue5051] test_update2 in test_os.py invalid due to os.environ.clear() followed by reliance on environ COMSPEC

2013-03-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: that's not the correct solution, ned. what that will do is when someone runs a combination of python and MSYS under wine, the test will be skipped incorrectly. thanks to the work that i did back in 2009, wine has now been improved signific

[issue5051] test_update2 in test_os.py invalid due to os.environ.clear() followed by reliance on environ COMSPEC

2013-03-18 Thread Luke Kenneth Casson Leighton
Luke Kenneth Casson Leighton added the comment: hi ned, well, the situation surrounding the bug-reporting that i was doing at the time was a general campaign of "this person is obviously wasting our time because they're developing yet another port/platform, that is obviously a wa

<    1   2