Re: Make a unique filesystem path, without creating the file

Marko Rauhamaa writes: > It is also correct that /dev/urandom depletes the entropy pool as > effectively as /dev/random. I think see what's confusing you: the above is a misconception that is probably held by lots of people. Entropy is not water and from a cryptographic

Re: Make a unique filesystem path, without creating the file

Steven D'Aprano : > On Tue, 23 Feb 2016 06:32 am, Marko Rauhamaa wrote: >> Under Linux, /dev/random is the way to go when strong security is >> needed. Note that /dev/random is a scarce resource on ordinary >> systems. > > That's actually incorrect, but you're not the only

good python tutorial

This site was recommended by a friend, it looks really well put together, I thought it might be of interest to people considering online tutorials. http://www.python-course.eu/index.php -- https://mail.python.org/mailman/listinfo/python-list

[issue26417] Default IDLE 2.7.11 configuration files are out-of-sync on OS X framework installs

New submission from Ned Deily: On OS X framework installs, the Mac-specific sub-makefiles do some important tailoring of IDLE/s config-extensions.def and config-main.def files, among other things changing Tk some Tk events for more appropriate keyboard bindings (e.g. "

[issue26366] Use “.. versionadded” over “.. versionchanged” where appropriate

Fred L. Drake, Jr. added the comment: For anyone following along only via the tracker, it's worth noting that proposals for new markup are welcome on the docs mailing list. More information is available at: https://mail.python.org/mailman/listinfo/docs --

Re: Make a unique filesystem path, without creating the file

Chris Angelico writes: > How much future are you expecting? This is old but its methodology still seems ok: http://saluc.engr.uconn.edu/refs/keymgr/blaze95minimalkeylength.pdf I also like this: http://cr.yp.to/talks/2015.10.05/slides-djb-20151005-a4.pdf Quote (slide

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 1:27 PM, Paul Rubin wrote: > 3) The default token length should be long enough to not have to "change > in the future". If the user wants a shorter token, they ask for that, > or can truncate a longer one that they receive from the default.

Re: Make a unique filesystem path, without creating the file

Steven D'Aprano writes: > https://www.python.org/dev/peps/pep-0506/ I didn't know about this! The discussion was all on mailing lists? A few things I suggest changing: 1) the default system RNG for Linux should be getrandom(2) on kernels that support it (3.17 and

[issue26323] Add assert_called() and assert_called_once() methods for mock objects

Changes by Raymond Hettinger : -- assignee: -> michael.foord ___ Python tracker ___

[issue26366] Use “.. versionadded” over “.. versionchanged” where appropriate

Raymond Hettinger added the comment: Fred, thanks for chiming in. Let's do close this one. -- nosy: +rhettinger resolution: -> not a bug status: open -> closed ___ Python tracker

Re: Make a unique filesystem path, without creating the file

On 2016-02-23, Ben Finney wrote: > Oscar Benjamin writes: >> What does unpredictable mean in this context? Maybe I'm reading too >> much into that... > > I think you may be, yes. The request in this thread requires making > direct use of

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 11:44 AM, Jon Ribbens wrote: > On 2016-02-23, Chris Angelico wrote: >> On Tue, Feb 23, 2016 at 11:26 AM, Jon Ribbens >> wrote: >>> On 2016-02-23, Chris Angelico wrote: On

Re: Make a unique filesystem path, without creating the file

On 2016-02-23, Chris Angelico wrote: > On Tue, Feb 23, 2016 at 11:26 AM, Jon Ribbens > wrote: >> On 2016-02-23, Chris Angelico wrote: >>> On Tue, Feb 23, 2016 at 11:08 AM, Jon Ribbens >>> wrote: >

Re: How the heck does async/await work in Python 3.5

On Mon, Feb 22, 2016 at 3:16 PM, Sven R. Kunze wrote: > Is something like shown in 12:50 ( cout << tcp_reader(1000).get() ) possible > with asyncio? (tcp_reader would be async def) loop = asyncio.get_event_loop() print(loop.run_until_complete(tcp_reader(1000))) --

Re: Make a unique filesystem path, without creating the file

On Tue, 23 Feb 2016 06:32 am, Marko Rauhamaa wrote: > Jon Ribbens : > >> Suppose you had code like this: >> >> filename = binascii.hexlify(os.urandom(16)).decode("ascii") >> >> Do we really think that is insecure or that there are any practical >> attacks against

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 11:26 AM, Jon Ribbens wrote: > On 2016-02-23, Chris Angelico wrote: >> On Tue, Feb 23, 2016 at 11:08 AM, Jon Ribbens >> wrote: If you generate 2**128 + 1 such numbers, you are *guaranteed*

Re: Make a unique filesystem path, without creating the file

Oscar Benjamin writes: > What does unpredictable mean in this context? Maybe I'm reading too > much into that... I think you may be, yes. The request in this thread requires making direct use of the “generate a new valid temporary fielsystem path” functionality

Re: Make a unique filesystem path, without creating the file

On 2016-02-23, Chris Angelico wrote: > On Tue, Feb 23, 2016 at 11:08 AM, Jon Ribbens > wrote: >>> If you generate 2**128 + 1 such numbers, you are *guaranteed* to >> >> ... have expired due to the heat death of the universe. > > Maybe... but by the

Re: Make a unique filesystem path, without creating the file

On Tue, 23 Feb 2016 05:17 am, Jon Ribbens wrote: > On 2016-02-22, Ethan Furman wrote: >> On 02/14/2016 04:08 PM, Ben Finney wrote: >>> I am unconcerned with whether there is a real filesystem entry of that >>> name; the goal entails having no filesystem activity for this. I

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 11:08 AM, Jon Ribbens wrote: > On 2016-02-22, Steven D'Aprano wrote: >> On Tue, 23 Feb 2016 05:48 am, Marko Rauhamaa wrote: >>> Jon Ribbens : I was under the impression that the point of

Re: Make a unique filesystem path, without creating the file

On 2016-02-22, Steven D'Aprano wrote: > On Tue, 23 Feb 2016 05:48 am, Marko Rauhamaa wrote: >> Jon Ribbens : >>> I was under the impression that the point of UUIDs is that you can be >>> *so* confident that there won't be a collision that for all

Re: Make a unique filesystem path, without creating the file

On 2016-02-23, Steven D'Aprano wrote: > On Tue, 23 Feb 2016 06:22 am, Jon Ribbens wrote: >> Suppose you had code like this: >> >> filename = binascii.hexlify(os.urandom(16)).decode("ascii") >> >> Do we really think that is insecure or that there are any practical >> attacks

Re: Make a unique filesystem path, without creating the file

On Tue, 23 Feb 2016 06:22 am, Jon Ribbens wrote: > Suppose you had code like this: > > filename = binascii.hexlify(os.urandom(16)).decode("ascii") > > Do we really think that is insecure or that there are any practical > attacks against it? It would be basically the same as saying that >

[issue26335] Make mmap.write return the number of bytes written like other write methods

Berker Peksag added the comment: Thanks for the patch, Jakub. I don't use mmap module much so I don't have an opinion about the feature, but it sounds reasonable. I left some review comments on Rietveld: http://bugs.python.org/review/26335/ -- components: +Extension Modules -IO,

Re: Make a unique filesystem path, without creating the file

On 22 Feb 2016 22:50, "Ben Finney" wrote: > > Ethan Furman writes: > > > On 02/14/2016 04:08 PM, Ben Finney wrote: > > > > > I am unconcerned with whether there is a real filesystem entry of that > > > name; the goal entails having no filesystem

Re: Make a unique filesystem path, without creating the file

On Tue, 23 Feb 2016 06:22 am, Paul Rubin wrote: > Chris Angelico writes: >>> I was under the impression that the point of UUIDs is that you can be >>> *so* confident that there won't be a collision that for all practical >>> purposes it's indistinguishable from being certain.

Re: Make a unique filesystem path, without creating the file

On Tue, 23 Feb 2016 05:48 am, Marko Rauhamaa wrote: > Jon Ribbens : > >> I was under the impression that the point of UUIDs is that you can be >> *so* confident that there won't be a collision that for all practical >> purposes it's indistinguishable from being

Re: Make a unique filesystem path, without creating the file

Marko Rauhamaa writes: http://www.2uo.de/myths-about-urandom/ >> I don't know what web pamphlet you mean, > The only one linked above. Oh, I wouldn't have called that a pamphlet. I could quibble with the writing style but the points in the article are basically correct.

[issue26416] Deprecate the regex_v8, telco, and spectral_norm benchmarks

Changes by Brett Cannon : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list

[issue26415] Out of memory, trying to parse a 35MB dict

New submission from A. Skrobov: I have a one-line module that assigns a tuple->int dictionary: holo_table = {(0, 0, 0, 0, 0, 0, 1, 41, 61, 66, 89): 9, (0, 0, 0, 70, 88, 98, 103, 131, 147, 119, 93): 4, [35MB skipped], (932, 643, 499, 286, 326, 338, 279, 200, 280, 262, 115): 5} When I try to

[issue26416] Deprecate the regex_v8, telco, and spectral_norm benchmarks

New submission from Brett Cannon: In the thread at https://mail.python.org/pipermail/speed/2016-February/000272.html it came up that the regex_v8, telco, and spectral_norm benchmarks are all very inconsistent. That means they should be deprecated. -- components: Benchmarks messages:

Re: Make a unique filesystem path, without creating the file

On 22Feb2016 12:34, Alan Bawden wrote: Cameron Simpson writes: On 16Feb2016 19:24, Alan Bawden wrote: So in the FIFO case, I might write something like the following: def make_temp_fifo(mode=0o600): while True:

[issue26414] os.defpath too permissive

Changes by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker ___ ___

[issue26414] os.defpath too permissive

Changes by Danek Duvall : -- nosy: +dhduvall ___ Python tracker ___ ___

Re: Make a unique filesystem path, without creating the file

On 02/22/2016 02:25 PM, Cameron Simpson wrote: On 22Feb2016 10:11, Ethan Furman wrote: On 02/14/2016 04:08 PM, Ben Finney wrote: I am unconcerned with whether there is a real filesystem entry of that name; the goal entails having no filesystem activity for this. I want a

[issue26414] os.defpath too permissive

New submission from John Beck: A bug has been filed against Solaris' internal version of Python, which is largely the same (including in this case) as the base version we get from python.org. The bug is that os.defpath starts with ':' and thus any Python script run with a null PATH environment

Re: Make a unique filesystem path, without creating the file

Ethan Furman writes: > On 02/14/2016 04:08 PM, Ben Finney wrote: > > > I am unconcerned with whether there is a real filesystem entry of that > > name; the goal entails having no filesystem activity for this. I want a > > valid unique filesystem path, without touching the

Re: Make a unique filesystem path, without creating the file

On 22Feb2016 10:11, Ethan Furman wrote: On 02/14/2016 04:08 PM, Ben Finney wrote: I am unconcerned with whether there is a real filesystem entry of that name; the goal entails having no filesystem activity for this. I want a valid unique filesystem path, without touching

[issue26366] Use “.. versionadded” over “.. versionchanged” where appropriate

Fred L. Drake, Jr. added the comment: If no one is planning to propose specific new markup for more fine-grained version annotations, this issue can be closed. -- ___ Python tracker

Re: How the heck does async/await work in Python 3.5

On 20.02.2016 07:53, Christian Gollwitzer wrote: If you have difficulties wit hthe overall concept, and if you are open to discussions in another language, take a look at this video: https://channel9.msdn.com/Shows/C9-GoingNative/GoingNative-39-await-co-routines MS has added coroutine

[issue26413] python 3.5.1 uses wrong registry in system-wide installation

Changes by Eryk Sun : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Windows AllUsers installation places uninstaller in user profile ___ Python tracker

[issue26388] Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True)

Mike Kaplinskiy added the comment: Looks like by signed CLA just made it through, so that should be settled. For the other bugs, it seems that overloading run_module & run_path seems to be getting a bit cumbersome, so it might make sense to have some sort of Runner object that has things like

[issue26413] python 3.5.1 uses wrong registry in system-wide installation

New submission from Mike: The installer for python 3.5.1 (observed with the x64-86 executable installer, assumed to happen with all installers) allows users to install python either just for themselves or do a system-wide installation (provided they have sufficient privileges). However, when

Re: Considering migrating to Python from Visual Basic 6 for engineering applications

BartC wrote: Our system must have been more advanced then, or designed for training. We used a time-sharing 'dec-system 10' and it was usually accessed via interactive terminals, either teletypes or the odd VDU. According to Wikipedia the first interactive version of Dartmouth BASIC appeared

Re: Make a unique filesystem path, without creating the file

Paul Rubin : >>> http://www.2uo.de/myths-about-urandom/ >> Did you post the link because you agreed with the Web pamphlet? > > I don't know what web pamphlet you mean, The only one linked above. Cryptography is tricky business, indeed. I know enough about it not to

Re: Make a unique filesystem path, without creating the file

Marko Rauhamaa writes: >> http://www.2uo.de/myths-about-urandom/ > Did you post the link because you agreed with the Web pamphlet? I don't know what web pamphlet you mean, but the right thing to use now is getrandom(2). The random/urandom interface was poorly designed and

[issue26403] Catch FileNotFoundError in socketserver.DatagramRequestHandler

Changes by desbma : -- title: Don't call sendto in socketserver.DatagramRequestHandler if there is nothing to send -> Catch FileNotFoundError in socketserver.DatagramRequestHandler ___ Python tracker

[issue26403] Don't call sendto in socketserver.DatagramRequestHandler if there is nothing to send

desbma added the comment: OK, so first part of this issue (sendto called even if no data has been written) is indeed a duplicate of https://bugs.python.org/issue1767511 sorry for that. For the second part of the issue (the exception not silenced), I have attached a new patch. --

Re: Make a unique filesystem path, without creating the file

Random832 : > On Mon, Feb 22, 2016, at 14:32, Marko Rauhamaa wrote: >> urandom() is not quite random and so should not be considered >> cryptographically airtight. >> >> Under Linux, /dev/random is the way to go when strong security is >> needed. Note that /dev/random is

[issue1767511] SocketServer.DatagramRequestHandler with empty response

Changes by desbma : -- nosy: +desbma ___ Python tracker ___ ___ Python-bugs-list

[issue26377] Tkinter dialogs will not close if root window not packed.

Sam Yeager added the comment: Updated script with the adding 'parent-Rootwin' to messagebox() arguments. The issue persists. Following advice in #26376: Ran script on Terminal. The issue disappears, and everything works normally. Running through IDLE, the issue returns. --

[issue26376] Tkinter root window won't close if packed.

Sam Yeager added the comment: Ran script on Terminal. The issue disappears, and everything works normally. Running through IDLE, the issue returns. Sorry, Terry. -- ___ Python tracker

Re: Make a unique filesystem path, without creating the file

On Mon, Feb 22, 2016, at 14:32, Marko Rauhamaa wrote: > urandom() is not quite random and so should not be considered > cryptographically airtight. > > Under Linux, /dev/random is the way to go when strong security is > needed. Note that /dev/random is a scarce resource on ordinary systems.

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 6:22 AM, Jon Ribbens wrote: >> Maybe, if everyone's cooperating. I'm not sure how they fare in the >> face of malice though. > > Suppose you had code like this: > > filename = binascii.hexlify(os.urandom(16)).decode("ascii") > > Do we really

Re: Make a unique filesystem path, without creating the file

Jon Ribbens : > Suppose you had code like this: > > filename = binascii.hexlify(os.urandom(16)).decode("ascii") > > Do we really think that is insecure or that there are any practical > attacks against it? It would be basically the same as saying that > urandom()

Re: Make a unique filesystem path, without creating the file

On 2016-02-22, Chris Angelico wrote: > On Tue, Feb 23, 2016 at 5:39 AM, Jon Ribbens > wrote: >> On 2016-02-22, Chris Angelico wrote: >>> On Tue, Feb 23, 2016 at 5:17 AM, Jon Ribbens >>> wrote:

Re: Make a unique filesystem path, without creating the file

Chris Angelico writes: >> I was under the impression that the point of UUIDs is that you can be >> *so* confident that there won't be a collision that for all practical >> purposes it's indistinguishable from being certain. > Maybe, if everyone's cooperating. I'm not sure how

Re: 0x80070570-The file or directory is corrupted and unreadable

El martes, 22 de diciembre de 2015, 13:46:01 (UTC-3), eryk sun escribió: > On Tue, Dec 22, 2015 at 8:02 AM, muizz hasan wrote: > > Hi there! I've been recently trying to install Python for Windows 10 > > and I've been encountering some issues. Every time i try to install >

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 5:39 AM, Jon Ribbens wrote: > On 2016-02-22, Chris Angelico wrote: >> On Tue, Feb 23, 2016 at 5:17 AM, Jon Ribbens >> wrote: >>> Weell, I have a lot of sympathy for that point, but on the

Re: PyPDF2 merge / out of memory

Le dimanche 21 février 2016 11:42:33 UTC+1, cpol...@gmail.com a écrit : > Hello, > > There is an issue with PyPDF2 and merging file > https://github.com/mstamy2/PyPDF2/issues/189 > > Does anybody know an alternate library to merge PDF and produce optimized pdf > file ? > > Thanks a lot > >

Re: Make a unique filesystem path, without creating the file

Jon Ribbens : > I was under the impression that the point of UUIDs is that you can be > *so* confident that there won't be a collision that for all practical > purposes it's indistinguishable from being certain. Yes, if you generate a random 128-bit number, it will

Re: Make a unique filesystem path, without creating the file

On 2016-02-22, Chris Angelico wrote: > On Tue, Feb 23, 2016 at 5:17 AM, Jon Ribbens > wrote: >> Weell, I have a lot of sympathy for that point, but on the other >> hand the whole concept of UUIDs ("import uuid") is predicated on the >> opposite

[issue26404] socketserver context manager

Aviv Palivoda added the comment: Only closing the server :). 1. Did the changes requested in the CR. 2. Changed the example's in xmlrpc.server, http.server to use context manager. 3. Changed the xmlrpc.server, http.server server implementation when running python -m {xmlrpc.server, http.server}

Re: Make a unique filesystem path, without creating the file

On 2016-02-22, Ethan Furman wrote: > On 02/14/2016 04:08 PM, Ben Finney wrote: >> I am unconcerned with whether there is a real filesystem entry of that >> name; the goal entails having no filesystem activity for this. I want a >> valid unique filesystem path, without touching

Re: Make a unique filesystem path, without creating the file

On Tue, Feb 23, 2016 at 5:17 AM, Jon Ribbens wrote: > On 2016-02-22, Ethan Furman wrote: >> On 02/14/2016 04:08 PM, Ben Finney wrote: >>> I am unconcerned with whether there is a real filesystem entry of that >>> name; the goal entails having no

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Alessandro Cucci added the comment: New patch after @martin.panter comments on Rietveld. I left only this: - ``'milliseconds'``: Append the hours, minutes, seconds and milliseconds. > vadmium 2016/02/21 23:30:20 > I think this should explain that fractions are truncated to zero, never >

Re: Make a unique filesystem path, without creating the file

On 02/14/2016 04:08 PM, Ben Finney wrote: I am unconcerned with whether there is a real filesystem entry of that name; the goal entails having no filesystem activity for this. I want a valid unique filesystem path, without touching the filesystem. This is impossible. If you don't touch the

[issue25136] Python doesn't find Xcode 7 stub libraries

Brett Cannon added the comment: We should update the devguide to specify that the command-line tools need to be installed and either explain or point to documentation on how to install the tools. -- nosy: +brett.cannon ___ Python tracker

[issue15216] Support setting the encoding on a text stream after creation

Changes by Andrei Dorian Duma : -- nosy: -andrei.duma ___ Python tracker ___

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Changes by Andrei Dorian Duma : -- nosy: -andrei.duma ___ Python tracker ___

[issue26411] Suggestion concerning compile-time warnings

Changes by Brett Cannon : -- resolution: -> not a bug status: open -> closed ___ Python tracker ___

[issue25801] ResourceWarning in test_zipfile64

Changes by SilentGhost : -- status: open -> languishing ___ Python tracker ___ ___

[issue26405] tkinter askopenfilename doubleclick issue on windows

Changes by SilentGhost : -- components: +Windows nosy: +gpolo, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware ___ Python tracker

[issue26411] Suggestion concerning compile-time warnings

Changes by SilentGhost : -- nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan, yselivanov ___ Python tracker ___

[issue25910] Fixing links in documentation

Changes by SilentGhost : -- status: open -> languishing ___ Python tracker ___ ___

[issue26281] Clear sys.path_importer_cache from importlib.invalidate_caches()

Brett Cannon added the comment: Sorry, this has not been decided upon yet. Since it's a change in semantics either I just need to make a decision or convince someone else to provide an opinion as to whether this change makes sense. -- ___ Python

Re: Make a unique filesystem path, without creating the file

Cameron Simpson writes: > On 16Feb2016 19:24, Alan Bawden wrote: >>So in the FIFO case, I might write something like the following: >> >>def make_temp_fifo(mode=0o600): >>while True: >>path = tempfile.mktemp() >>try: >>

[issue26412] Segmentation Fault: 11

Christian Heimes added the comment: pysodium is not part of Python's standard library. Please report 3rd party bugs in the project's bug tracker. -- nosy: +christian.heimes resolution: -> third party stage: -> resolved status: open -> closed ___

[issue26412] Segmentation Fault: 11

New submission from Payden Comer: A "Segmentation Fault:11" crash occurs on OS X El Captain when using `return pysodium.sodium.crypto_box_beforenm(clientpub, serverprivatekey)`, with args as None, serverprivatekey, rather than a traceback dissallowing a NoneType Argument. Crash Log attached.

[issue26281] Clear sys.path_importer_cache from importlib.invalidate_caches()

Anish Shah added the comment: Hi Brett, I'm looking for some issues to solve. Is this issue confirmed? Can I work on this? -- ___ Python tracker ___

[issue26396] Create json.JSONType

Changes by Anish Shah : -- nosy: +anish.shah ___ Python tracker ___ ___

[issue22234] urllib.parse.urlparse accepts any falsy value as an url

Changes by Anish Shah : -- nosy: +anish.shah ___ Python tracker ___ ___

[issue26408] pep-8 requires a few corrections

Barry A. Warsaw added the comment: On Feb 22, 2016, at 02:20 PM, Georg Brandl wrote: >Georg Brandl added the comment: > >-Consistency within one module or function is most important. >+Consistency within one module or function is the most important. > >You left out "thing" from the patch; is

Re: Considering migrating to Python from Visual Basic 6 for engineering applications

On 22/02/2016 10:46, Steven D'Aprano wrote: On Mon, 22 Feb 2016 08:52 am, Jussi Piitulainen wrote: BartC writes: IIRC, the first programming exercise I ever did (in 1976 using Algol 60) involved reading 3 numbers from the teletype and working out if those could form sides of a triangle.

[issue26410] "incompatible pointer type" while compiling Python3.5.1

STINNER Victor added the comment: This issue is a duplicate of the issue #26161, waybe we can backport the changeset ff68ffcc6244 to the Python 3.5 branch. -- nosy: +haypo ___ Python tracker

Re: avoid for loop calling Generator function

On Mon, Feb 22, 2016 at 8:38 AM, Arshpreet Singh wrote: > On Monday, 22 February 2016 19:05:24 UTC+5:30, Peter Otten wrote: >> or the slightly less convoluted >> >> sys.stdout.writelines(map("{}\n".format, read_pdf("book.pdf"))) > > Actually I am using this function in Android

Re: avoid for loop calling Generator function

On Tue, Feb 23, 2016 at 2:38 AM, Arshpreet Singh wrote: >> next(filter(print, read_pdf("book.pdf")), None) > > Why we are w=using filter here? It's a beautiful hack. It'll filter according to the "print" predicate, which always returns None, and will thus filter everything

[issue26395] asyncio does not support yielding from recvfrom (socket/udp)

Changes by Simon Bernier St-Pierre : -- status: open -> closed ___ Python tracker ___

Re: avoid for loop calling Generator function

On Monday, 22 February 2016 19:05:24 UTC+5:30, Peter Otten wrote: > Arshpreet Singh wrote: > > > Hi, I am converting PDF into text file, I am using following code. > > > > from pypdf2 import PdfFileReader > > > > def read_pdf(pdfFileName): > > > > pdf = PdfFileReader(pdfFileName) > > > >

[issue26411] Suggestion concerning compile-time warnings

New submission from Devyn Johnson: I understand that compile-time warnings can typically be ignored. However, from my experience with programming (C STD-2011, for instance), "weird bugs", non-easily-replicable bugs, and odd behaviors disappear when warnings like this are fixed. I also

[issue26410] "incompatible pointer type" while compiling Python3.5.1

New submission from Devyn Johnson: When compiling Python3.5.1 on Ubuntu 15.10 (64-bit), I see three "incompatible pointer type" warnings (copy-pasted below). I understand that they can be ignored. However, from my experience with programming (in C STD-2011), "weird bugs" and other odd

[issue25080] The example-code for making XML-RPC requests through proxy, fail!

Berker Peksag added the comment: This has been fixed in cf842a8ccb77. Thank you for reporting this, Kostis! -- nosy: +berker.peksag resolution: -> out of date stage: needs patch -> resolved status: open -> closed versions: -Python 3.4 ___ Python

Re: Considering migrating to Python from Visual Basic 6 for engineering applications

On Mon, Feb 22, 2016, at 05:46, Steven D'Aprano wrote: > Jussi, I think you have an inflated expectation of what was available in > 1976. Command line? What's that? Programs ran in batch mode, > and 'interactive' meant that you could easily slip out one punched card, > replace it with a different

[issue26408] pep-8 requires a few corrections

Georg Brandl added the comment: -Consistency within one module or function is most important. +Consistency within one module or function is the most important. You left out "thing" from the patch; is that intended? -- ___ Python tracker

[issue26408] pep-8 requires a few corrections

Roundup Robot added the comment: New changeset 43d612fc6b12 by Barry Warsaw in branch 'default': Gramatical and other improvements given by thefourtheye. https://hg.python.org/peps/rev/43d612fc6b12 -- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed

[issue26249] Change PyMem_Malloc to use PyObject_Malloc allocator?

Catalin Gabriel Manciu added the comment: I've just posted the results to an OpenStack Swift benchmark run using the patch from my proposition, issue #26382. Victor's patch, applied to CPython 2.7, adds an extra 1% compared to mine (which improved throughput by 1%), effectively doubling the

[issue26408] pep-8 requires a few corrections

Barry A. Warsaw added the comment: Thanks! I like some of the changes, and may tweak a few others. Thanks for the contribution. -- ___ Python tracker

[issue26408] pep-8 requires a few corrections

Changes by Barry A. Warsaw : -- assignee: docs@python -> barry ___ Python tracker ___ ___

[issue26408] pep-8 requires a few corrections

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue26408] pep-8 requires a few corrections

Georg Brandl added the comment: I can't really comment on the grammar changes, but the rest looks good to me. This is not very smooth, in both versions: -Consistency within one module or function is most important. +Consistency within one module or function is the most important thing. -But

  1   2   >