Mateusz Loskot added the comment:
Possibly, the new partial-input mode of the parser
(https://bugs.python.org/issue46521#msg412832) will improve this issue in 3.11.
I'm going to play with it soon and I will report back.
--
___
Python tracker
Mateusz Loskot added the comment:
Not quite the answer I'd like to received, but thank you very much for the
explanation.
I've submitted pull request removing the deprecated FAQ entry
https://github.com/python/cpython/pull/30925
--
___
Python
Mateusz Loskot added the comment:
Irit, I can and I will submit a patch.
However, I'm very keen to learn what is an alternative solution then to
distinguish hard invalid from incomplete input. IOW, what would be the new way
of achieving what's described in the old FAQ?
I believe it would
New submission from Mateusz Loskot :
Something has changed in Python 3.7 through 3.10 (I'm observing it in 3.10) in
behaviour of the Python C API function Py_CompileString such that for an
incomplete input it no longer raises
SyntaxError: "unexpected EOF while parsing"
but
Indent
Change by Mateusz Loskot :
--
nosy: +mloskot
___
Python tracker
<https://bugs.python.org/issue39511>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Mateusz Loskot <mate...@loskot.net>:
--
nosy: +mloskot
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue14597>
___
__
Mateusz Loskot added the comment:
Re msg238016, I confirm python-3.5.0a2-fdvalidation.patch fixes the problem for
Python 3.5.0a4 and VS2013.
The only issue I encountered was with HAVE_FSTAT which is missing from
PC/pyconifg.h, so I edited the patch and removed the check if
defined(HAVE_FSTAT
On 13 December 2014 at 12:24, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
Mateusz Loskot wrote:
On 12 December 2014 at 12:26, Chris Angelico ros...@gmail.com wrote:
On Fri, Dec 12, 2014 at 10:21 PM, Mateusz Loskot mate...@loskot.net
wrote:
I've got several cases which
On 11 December 2014 at 19:20, Chris Angelico ros...@gmail.com wrote:
On Fri, Dec 12, 2014 at 4:34 AM, Mateusz Loskot mate...@loskot.net wrote:
If a class member function simply tests something and
returns a b::oolean call it
def is_whatever_you_are_testing_for():
pass
like 'is_even
On 12 December 2014 at 12:26, Chris Angelico ros...@gmail.com wrote:
On Fri, Dec 12, 2014 at 10:21 PM, Mateusz Loskot mate...@loskot.net wrote:
I've got several cases which are not obvious to me.
For instance, class Foo has a boolean attribute, read-write,
which I see a couple of realisations
On 12 December 2014 at 22:14, Chris Angelico ros...@gmail.com wrote:
On Sat, Dec 13, 2014 at 8:03 AM, Mateusz Loskot mate...@loskot.net wrote:
On 12 December 2014 at 12:26, Chris Angelico ros...@gmail.com wrote:
On Fri, Dec 12, 2014 at 10:21 PM, Mateusz Loskot mate...@loskot.net wrote:
I've
predicates?
[1] *Naming Conventions* by Thorsten Kampe
https://mail.python.org/pipermail/python-list/2007-June/438156.html
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
https://mail.python.org/mailman/listinfo/python-list
Mateusz Loskot added the comment:
FYI, I've got it confirmed fix for the bug in VS has been released [1]
We have fixed this behavior for the next major release, Visual Studio 14. The
fix is present in the Visual Studio 14 CTP that was released earlier this
month.
[1]
https
New submission from Mateusz Loskot:
While building Python 3.2 or Python 3.4 with Visual Studio 2013 on Windows 8.1,
pythoncore.vcxproj fails to build due to illformed pre-link event command.
(FYI, I have upgraded all .vcxproj files to VS2013 locally.)
Here is the command and the error:
pre
Mateusz Loskot added the comment:
I have just tested Windows GUI application built against Python 3.2.1 with
is_valid_fd patch according to http://hg.python.org/cpython/rev/f15943505db0/
All built using VS2012.
Again, I can confirm that is_valid_fd does NOT solve the problem.
Here is extract
Mateusz Loskot added the comment:
@Antoine (Re msg197480)
I'm not sure which minor version of Python 3.2 it was, but in my comment in
msg187362, I confirmed that I have tested the later version with added
is_valid_fd function. As far as I understand, the changes in
http://hg.python.org
Mateusz Loskot added the comment:
On 11 September 2013 12:34, Antoine Pitrou rep...@bugs.python.org wrote:
I'm not sure which minor version of Python 3.2 it was, but in my
comment in msg187362, I confirmed that I have tested the later
version with added is_valid_fd function. As far as I
Mateusz Loskot added the comment:
On 12 September 2013 00:06, Antoine Pitrou rep...@bugs.python.org wrote:
Shortly, is_valid_fd always returns true because fd 0 is always
false as my tests with Visual Studio 2012
Well, that's not all there is, is_valid_fd() does other checks before
Mateusz Loskot added the comment:
This is still an issue in VS 2012 Version 11.0.60610.01 Update 3
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17797
Mateusz Loskot added the comment:
I've just got an update on the bug report [1] I submitted to Microsoft.
The Visual C++ team confirmed It does appear to be a regression from Visual
Studio 2010.
So, it's not a bug in Python, but I think it may be important for Python to
consider applying some
New submission from Mateusz Loskot:
In pythonrun.c, there is function initstdio() with the following test:
static int
initstdio(void)
{
...
/* Set sys.stdin */
fd = fileno(stdin);
/* Under some conditions stdin, stdout and stderr may not be connected
* and fileno() may point
Mateusz Loskot added the comment:
Yes, it does. In file Modulfileio.c, in function fileio_init, there is this
code:
if (fd = 0) {
if (check_fd(fd))
goto error;
self-fd = fd;
self-closefd = closefd;
}
The check_fd tests:
if (!_PyVerify_fd(fd
Mateusz Loskot added the comment:
In file Modulfileio.c,
I messed the path and filename above I meant: In file Modules/_io/fileio.c,
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17797
Mateusz Loskot added the comment:
Replacing if the current test in Python 3.2
if (fd 0)
with
if (check_fd(fd) 0)
Seems to be a working solution.
I just noticed, that in current Python/pythonrun.c in the repo, there the fd
0 tests have been replaced with new function is_valid_fd
--
From: Mateusz Loskot mate...@loskot.net
Date: 19 October 2012 13:58
Subject: Format of datetime dump
To: yaml-c...@lists.sourceforge.net
Hi,
Given this snippet:
yaml.dump({'date':datetime.datetime.now()})
{date: !!timestamp '2012-10-19 01:32:41.674322'}\n
Could anyone enlighten me why
Mateusz Loskot mate...@loskot.net added the comment:
Chris Withers' note clarifies it to me, that this should be Python-level rather
than C-level documentation. Then the note under __new__() in 3. Data model
seems right.
Simply, I expected to have some notes in C API too
Side note: as mainly
Changes by Mateusz Loskot mate...@loskot.net:
--
nosy: +mloskot
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4442
___
___
Python-bugs-list
Mateusz Loskot mate...@loskot.net added the comment:
Is this report about documenting of the concept of immutable types in Python in
general or regarding existing built-in types, like datetime.datetime?
Generally, the concept of immutable type with relation to tp_new is mentioned
(sneaked
New submission from Mateusz Loskot mate...@loskot.net:
The chapter '2. Defining New Types in the Python 3.2 documentation [1] does
not cover all important elements, especially in the subsection 2.1.4.
Subclassing other types.
The accepted PEP 253 [2] provides much more detailed and thorough
Mateusz Loskot mate...@loskot.net added the comment:
Similar request has been rejected in response to the Issue 621526 [1],
but I'm not proposing to include PEP into docs, but to update and improve docs
with material discussed in accepted PEPs.
[1] http://bugs.python.org/issue621526
Mateusz Loskot mate...@loskot.net added the comment:
I reported issue 15029 [1] which may be related to this one.
[1] http://bugs.python.org/issue15029
--
nosy: +mloskot
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue621526
xyz.flag = 0# error due to no write access
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
http://mail.python.org/mailman/listinfo/python-list
] https://github.com/mloskot/workshop/blob/master/python/
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
//
// A quick and dirty C++ version of the C program presented in Python FAQ:
// http://docs.python.org/py3k/faq/extending.html#how-do-i-tell-incomplete-input-from-invalid-input
are
created and returned back, etc.
I understand it's difficult to discuss it without long essays or without
providing the code, etc.
So, I can only discuss and investigate building blocks I use.
Anyway, thanks for your comments.
Best regards,
-
--
Mateusz Loskot
http://mateusz.loskot.net
--
View
On 23/09/11 00:47, Mark Hammond wrote:
On 20/09/2011 8:34 PM, Mateusz Loskot wrote:
I'm trying to dig out details about what exactly is the return
value the of PyEval_EvalCodeEx function in Python 3.x
The documentation is sparse, unfortunately.
Perhaps I'm looking at wrong function.
My aim
PyEval_EvalCode return object:
PyObject* evalRet = ::PyEval_EvalCode(...);
But, I can't find any details what the evalRet actually is.
Any pointers would be helpful.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
Hi,
I'm wondering, why PyImport_ExecCodeModule function takes char*
instead of const char*?
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
--
http://mail.python.org/mailman/listinfo/python-list
37 matches
Mail list logo
