rigin), origin=origin)
18 return ret
19
20 sys.meta_path.append(IdeHelper)
which I'm on the right direction with. Unfortunately, I'm getting errors
while
importing a subpackage. With 'import top.child1' the error is
ModuleNotFoundError: No module named 'top.ch
Hello,
I would like to develop Mobile Applications using the Kivy Python Framework
but I am having difficulty and these are the errors I am finding "
C:\WINDOWS\system32>python3 --version Python was not found; run without
arguments to install from the Microsoft Store, or disable this
ponential forms for errors, specially when
starting to play with exponents: 6.67430E-11 ± 1.5E-15.
--
Ángel GR
--
https://mail.python.org/mailman/listinfo/python-list
On 19/12/2022 09.14, MRAB wrote:
On 2022-12-19 14:10, Peter J. Holzer wrote:
On 2022-12-19 09:25:17 +1100, Chris Angelico wrote:
On Mon, 19 Dec 2022 at 07:57, Stefan Ram wrote:
> G = Decimal( 6.6743015E-11 )
> r = Decimal( 6.371E6 )
> M = Decimal( 5.9722E24 )
What's the point of using Decimal
On 17/12/2022 18:55, Stefan Ram wrote:
> Grant Edwards writes:
>> Yes, fixed point (or decimal) is a better fit for what he's doing. but
>> I suspect that floating point would be a better fit for the problem
>> he's trying to solve.
>
> I'd like to predict that within the next ten posts in this
On 19/12/22 9:24 am, Stefan Ram wrote:
So what's the time until a mass of one gram
arrives at the ground versus a mass of ten grams? I think
one needs "Decimal" to calculate this!
Or you can be smarter about how you calculate it.
Differentiating t with respect to m gives
dt/dm = -0.5 * sqr
On 2022-12-19 15:14:14 +, MRAB wrote:
> On 2022-12-19 14:10, Peter J. Holzer wrote:
> > He also interpreted the notation "6.67430(15)E-11" wrong. The
> > digits in parentheses represent the uncertainty in the same number of
> > last digits. So "6.67430(15)E-11" means "something between 6.67430E
On 2022-12-19 14:10, Peter J. Holzer wrote:
On 2022-12-19 09:25:17 +1100, Chris Angelico wrote:
On Mon, 19 Dec 2022 at 07:57, Stefan Ram wrote:
> G = Decimal( 6.6743015E-11 )
> r = Decimal( 6.371E6 )
> M = Decimal( 5.9722E24 )
What's the point of using Decimal if you start with nothing more th
On 12/19/2022 9:10 AM, Peter J. Holzer wrote:
On 2022-12-19 09:25:17 +1100, Chris Angelico wrote:
On Mon, 19 Dec 2022 at 07:57, Stefan Ram wrote:
G = Decimal( 6.6743015E-11 )
r = Decimal( 6.371E6 )
M = Decimal( 5.9722E24 )
What's the point of using Decimal if you start with nothing more than
On 2022-12-19 09:25:17 +1100, Chris Angelico wrote:
> On Mon, 19 Dec 2022 at 07:57, Stefan Ram wrote:
> > G = Decimal( 6.6743015E-11 )
> > r = Decimal( 6.371E6 )
> > M = Decimal( 5.9722E24 )
>
> What's the point of using Decimal if you start with nothing more than
> float accuracy?
Right. He als
On 19Dec2022 08:53, Cameron Simpson wrote:
I'm no expert on floating point coding for precision, but I believe
that trying to work with values "close together" in magnitude is
important because values of different scales inherently convert one of
them to the other scale (i.e. similar sized exp
On 19/12/22 6:35 am, Paul St George wrote:
So I am working on a physics paper with a colleague. We have a theory about
Newtons Cradle.
We want to illustrate the paper with animations.
Because there is a problem, I am investigating in all areas. ... I would like
to be in control of or fully aw
On Mon, 19 Dec 2022 at 07:57, Stefan Ram wrote:
> G = Decimal( 6.6743015E-11 )
> r = Decimal( 6.371E6 )
> M = Decimal( 5.9722E24 )
What's the point of using Decimal if you start with nothing more than
float accuracy?
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
On 18Dec2022 18:35, Paul St George wrote:
So I am working on a physics paper with a colleague. We have a theory about
Newtons Cradle. We answer the question why when you lift and drop balls 1 and
2, balls 4 and 5 rise up. I could say more, but ... (if you are interested
please write to me).
On 18/12/2022 10.55, Stefan Ram wrote:
Grant Edwards writes:
Yes, fixed point (or decimal) is a better fit for what he's doing. but
I suspect that floating point would be a better fit for the problem
he's trying to solve.
I'd like to predict that within the next ten posts in this
thread
So I am working on a physics paper with a colleague. We have a theory about
Newtons Cradle. We answer the question why when you lift and drop balls 1 and
2, balls 4 and 5 rise up. I could say more, but ... (if you are interested
please write to me).
We want to illustrate the paper with animatio
On Sun, 18 Dec 2022 11:14:28 -0500, Dennis Lee Bieber wrote:
> .. And maybe lament the days when a 3-digit result was acceptable in
> math class -- being the typical capability in reading a standard (10"
> scale) slide rule.
Arguably more thought was given to what those three digits meant in the
Thanks for filling us in! I wouldn't think the animations themselves
would need such precision, though perhaps the calculations of the forces
and motions do. One way to check might be to perturb the initial
conditions a bit and see if the changes in the motions seem to be
correspondingly smal
So I am working on a physics paper with a colleague. We have a theory about
Newtons Cradle. We answer the question why when you lift and drop balls 1 and
2, balls 4 and 5 rise up. I could say more, but ... (if you are interested
please write to me).
We want to illustrate the paper with animatio
trivial using the conversion function of your
choice. Handling errors or what to do with something like a blank or NA are
nice ideas if asked about.
My answer would be to ask if this was an assignment where they are EXPECTED to
do things a certain way to master a concept, or part of a serious
On Sun, 18 Dec 2022 at 09:46, Stefan Ram wrote:
>
> Grant Edwards writes:
> >Yes, fixed point (or decimal) is a better fit for what he's doing. but
> >I suspect that floating point would be a better fit for the problem
> >he's trying to solve.
>
> I'd like to predict that within the next ten po
On 18/12/2022 01.39, Peter J. Holzer wrote:
On 2022-12-17 12:51:17 +0100, Paul St George wrote:
I have a large/long array of numbers in an external file. The numbers
look like this:
-64550.727
-64511.489
-64393.637
[...]
When I bring the numbers into my code, they are Strings. To use the
num
On 12/17/2022 3:45 PM, Paul St George wrote:
Thanks to all!
It was the rounding rounding error that I needed to avoid (as Peter J. Holzer
suggested). The use of decimal solved it and just in time. I was about to
truncate the number, get each of the characters from the string mantissa, and
then
On 2022-12-17 21:45:06 +0100, Paul St George wrote:
> It was the rounding rounding error that I needed to avoid (as Peter J.
> Holzer suggested). The use of decimal solved it and just in time. I
> was about to truncate the number, get each of the characters from the
> string mantissa, and then do s
On Sun, 18 Dec 2022 at 08:22, Grant Edwards wrote:
>
> On 2022-12-17, Chris Angelico wrote:
>
> >> It was the rounding rounding error that I needed to avoid (as Peter
> >> J. Holzer suggested). The use of decimal solved it and just in
> >> time. I was about to truncate the number, get each of the
On 2022-12-17, Chris Angelico wrote:
>> It was the rounding rounding error that I needed to avoid (as Peter
>> J. Holzer suggested). The use of decimal solved it and just in
>> time. I was about to truncate the number, get each of the
>> characters from the string mantissa, and then do something
On Sun, 18 Dec 2022 at 07:46, Paul St George wrote:
>
> Thanks to all!
> It was the rounding rounding error that I needed to avoid (as Peter J. Holzer
> suggested). The use of decimal solved it and just in time. I was about to
> truncate the number, get each of the characters from the string man
Thanks to all!
It was the rounding rounding error that I needed to avoid (as Peter J. Holzer
suggested). The use of decimal solved it and just in time. I was about to
truncate the number, get each of the characters from the string mantissa, and
then do something like this:
64550.727
64550 + (7
On 12/17/2022 1:41 PM, Mats Wichmann wrote:
On 12/17/22 07:15, Thomas Passin wrote:
You have strings, and you want to end up with numbers. The numbers
are not integers. Other responders have gone directly to whether you
should use float or decimal as the conversion, but that is a secondary
m
On 12/17/22 07:15, Thomas Passin wrote:
You have strings, and you want to end up with numbers. The numbers are
not integers. Other responders have gone directly to whether you should
use float or decimal as the conversion, but that is a secondary matter.
If you have integers, convert with
i
You have strings, and you want to end up with numbers. The numbers are
not integers. Other responders have gone directly to whether you should
use float or decimal as the conversion, but that is a secondary matter.
If you have integers, convert with
integer = int(number_string)
If you don't
On 2022-12-17 12:51:17 +0100, Paul St George wrote:
> I have a large/long array of numbers in an external file. The numbers
> look like this:
>
> -64550.727
> -64511.489
> -64393.637
[...]
>
> When I bring the numbers into my code, they are Strings. To use the
> numbers in my code, I want to chan
On 17/12/2022 11:51, Paul St George wrote:
> I have a large/long array of numbers in an external file. The numbers look
> like this:
>
> -64550.727
> -64511.489
> -64393.637
> -64196.763
> -63920.2
> When I bring the numbers into my code, they are Strings. To use the
> numbers in my code, I wan
https://docs.python.org/3/library/decimal.html
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Python-list on
behalf of Paul St George
Sent: Saturday, December 17, 2022 6:51:17 AM
To: python-list@python.org
Subject: String to Float, without introducing
I have a large/long array of numbers in an external file. The numbers look like
this:
-64550.727
-64511.489
-64393.637
-64196.763
-63920.2
-63563.037
-63124.156
-62602.254
-61995.895
-61303.548
-60523.651
-59654.66
...
When I bring the numbers into my code, they are Strings. To use the numbers i
On Sunday, October 9, 2022 at 12:09:45 PM UTC+2, Antoon Pardon wrote:
> I would like a tool that tries to find as many syntax errors as possible
> in a python file. I know there is the risk of false positives when a
> tool tries to recover from a syntax error and proceeds but I would
On 2022-10-11 14:11:56 -0400, Thomas Passin wrote:
> To bring things back to the context of the original post, actual web
> browsers are extremely tolerant of HTML syntax errors (including incorrect
> nesting of tags) in the documents they receive.
HTML5 actually specifies exactly how t
gt;
> > > if condition # no colon
> > > code
> > > else:
> > > code
> > >
> > > To actually "restart" parsing, you have to make a guess of some sort.
> >
> > Right. At least one of the papers on parsing I read over
On Thu, 13 Oct 2022 at 11:23, dn wrote:
> # add an extra character within identifier, as if 'new' identifier
> 28 assert expected_value == fyibonacci_number
> UUU
>
> # these all trivial SYNTAX errors - could have trie
> code
> >
> > To actually "restart" parsing, you have to make a guess of some sort.
>
> Right. At least one of the papers on parsing I read over the last few
> years (yeah, I really should try to find them again) argued that the
> vast majority of syntax
On 09/10/2022 23.09, Antoon Pardon wrote:
I would like a tool that tries to find as many syntax errors as possible
in a python file. I know there is the risk of false positives when a
tool tries to recover from a syntax error and proceeds but I would
prefer that over the current python
sort.
Right. At least one of the papers on parsing I read over the last few
years (yeah, I really should try to find them again) argued that the
vast majority of syntax errors is either a missing token, a superfluous
token or a combination of the the two. So one strategy with good results
is to h
if it only showed one error at a
time, it would make quick work of correcting mistakes. And it wouldn't
need to trigger an entire tool chain each time.
Aye.
I've got my editor (vim) configured to run an autoformatter on my code
when I save (this can be turned off, and parse err
parser can do some
error correction in mid-flight, for the purposes of a programming editor
(as opposed to one that has to build a correct program).
One editor that seems to do what the OP wants is Visual Studio Code. It
will mark apparent errors - not just syntax errors - not limited to one
resulting treelike structure has
names like DOM.
To bring things back to the context of the original post, actual web
browsers are extremely tolerant of HTML syntax errors (including
incorrect nesting of tags) in the documents they receive. They usually
recover silently from errors and are able to
resent aspects of what it sees. The resulting treelike structure has
> > names like DOM.
>
> To bring things back to the context of the original post, actual web
> browsers are extremely tolerant of HTML syntax errors (including
> incorrect nesting of tags) in the documents they recei
, actual web
browsers are extremely tolerant of HTML syntax errors (including
incorrect nesting of tags) in the documents they receive. They usually
recover silently from errors and are able to display the rest of the
page. Usually they manage this correctly. The OP would like to have a
can be very powerful as things interact.
Oh absolutely. That's why there are languages designed to help you
define other languages.
> In effect the errors in the web situation have such analogies too as in what
> happens if a region of HTML is not well-formed or uses a keyword not
&g
thing with DirEntry fields /
methods
From: Python-list on
behalf of avi.e.gr...@gmail.com
Date: Monday, October 10, 2022 at 10:11 PM
To: python-list@python.org
Subject: RE: What to use for finding as many syntax errors as possible.
*** Attention: This is an external email. Use caution respondin
Op 10/10/2022 om 19:08 schreef Robert Latest via Python-list:
Antoon Pardon wrote:
I would like a tool that tries to find as many syntax errors as possible
in a python file.
I'm puzzled as to when such a tool would be needed. How many syntax errors can
you realistically put into a s
Op 10/10/2022 om 19:08 schreef Robert Latest via Python-list:
Antoon Pardon wrote:
> I would like a tool that tries to find as many syntax errors as possible
> in a python file.
I'm puzzled as to when such a tool would be needed. How many syntax errors can
you realistically put in
uages" that complement each other. Some running programs, especially
ones that use asynchronous methods like threads or callbacks on events, such
as a GUI, can effectively do similar things.
In effect the errors in the web situation have such analogies too as in what
happens if a region of HTML i
disparate objects to live together. Python is far from
the most complex but as noted, it is not trivial to evaluate even the syntax
past errors.
But I admit it is fun and a challenge to learn both kinds and I spent much
of my time doing so. I like the flexibility of seeing different approaches
and
On Tue, 11 Oct 2022 at 14:26, wrote:
>
> I stand corrected Chris, and others, as I pay the sin tax.
>
> Yes, there are many kinds of errors that logically fall into different
> categories or phases of evaluation of a program and some can be determined
> by a more static analysi
On Tue, 11 Oct 2022 at 14:13, wrote:
> With the internet today, we are used to expecting error correction to come
> for free. Do you really need one of every 8 bits to be a parity bit, which
> only catches may half of the errors...
Fortunately, we have WAY better schemes than simp
I stand corrected Chris, and others, as I pay the sin tax.
Yes, there are many kinds of errors that logically fall into different
categories or phases of evaluation of a program and some can be determined
by a more static analysis almost on a line by line (or "statement" or
&
Cameron, or OP if you prefer,
I think by now you have seen a suggestion that languages make choices and
highly structured ones can be easier to "recover" from errors and try to
continue than some with way more complex possibilities that look rather
unstructured.
What is the error in
upper() method on None, it is an error to try to use a local
variable you haven't assigned to yet, and it is an error to open a
file that doesn't exist. But not one of these is a *syntax* error.
Syntax errors are detected at the parsing stage, before any code gets
run. The vast majori
Michael,
A reasonable question. Python lets you initialize variables but has no
explicit declarations. Languages differ and I juggle attributes of many in
my mind and am reacting to the original question NOT about whether and how
Python should report many possible errors all at once but how ANY
?
My guess is that finding 100 errors might turn out to be misleading.
If you
fix just the first, many others would go away. If you spell a variable
name
wrong when declaring it, a dozen uses of the right name may cause errors.
Should you fix the first or change all later ones?
How does one
On Tue, 11 Oct 2022 at 09:18, Cameron Simpson wrote:
>
> On 11Oct2022 08:02, Chris Angelico wrote:
> >There's a huge difference between non-fatal errors and syntactic
> >errors. The OP wants the parser to magically skip over a fundamental
> >syntactic error an
On 09/10/2022 10.49, Avi Gross wrote:
My guess is that finding 100 errors might turn out to be misleading.
If you
fix just the first, many others would go away. If you spell a variable name
wrong when declaring it, a dozen uses of the right name may cause errors.
Should you fix the first or
On 11Oct2022 08:02, Chris Angelico wrote:
There's a huge difference between non-fatal errors and syntactic
errors. The OP wants the parser to magically skip over a fundamental
syntactic error and still parse everything else correctly. That's
never going to work perfectly, and
Antoon Pardon wrote:
> I would like a tool that tries to find as many syntax errors as possible
> in a python file.
I'm puzzled as to when such a tool would be needed. How many syntax errors can
you realistically put into a single Python file before compiling it for the
first time?
Michael F. Stemper wrote:
> How does one declare a variable in python? Sometimes it'd be nice to
> be able to have declarations and any undeclared variable be flagged.
To my knowledge, the closest to that is using __slots__ in class definitions.
Many a time have I assigned to misspelled class memb
wrote:
> Cameron,
>
> Your suggestion makes me shudder!
Me, too
> Removing all earlier lines of code is often guaranteed to generate errors as
> variables you are using are not declared or initiated, modules are not
> imported and so on.
all of which aren't syntax error
try to find the end of that function and resume checking the
next function. But what if a function defines local functions within it?
What if the mistake in one line of code could still allow checking the next
line rather than skipping it all?
My guess is that finding 100 errors might turn out to
> an error of syntax *by definition* makes parsing the rest of the file
> > dubious.
>
> Dubious but still useful.
There's a huge difference between non-fatal errors and syntactic
errors. The OP wants the parser to magically skip over a fundamental
syntactic error and stil
On 2022-10-10 09:23:27 +1100, Chris Angelico wrote:
> On Mon, 10 Oct 2022 at 06:50, Antoon Pardon wrote:
> > I just want a parser that doesn't give up on encoutering the first syntax
> > error. Maybe do some semantic checking like checking the number of
> > parameters.
>
> That doesn't make sens
thought that
some IDEs should make the first syntax error very obvious and easy to go
to, and an obvious indication that the file as a whoe is syntacticly
good/bad. If you have such, between them you could fairly easily resolve
syntax errors rapidly, perhaps rapidly enough to make up for a
stop-
Op 10/10/2022 om 00:45 schreef Cameron Simpson:
On 09Oct2022 21:46, Antoon Pardon wrote:
Is it that onerous to fix one thing and run it again? It was once
when you
handed in punch cards and waited a day or on very busy machines.
Yes I find it onerous, especially since I have a pipeline wit
On 10Oct2022 00:41, avi.e.gr...@gmail.com wrote:
Your suggestion makes me shudder!
And fair enough too. I don't do this for me, I'm just suggesting an
approach which might bring something to Antoon's objective.
Removing all earlier lines of code is often guaranteed to gen
Cameron,
Your suggestion makes me shudder!
Removing all earlier lines of code is often guaranteed to generate errors as
variables you are using are not declared or initiated, modules are not
imported and so on.
Removing just the line or three where the previous error happened would also
have a
On 10/9/2022 1:29 PM, Peter J. Holzer wrote:
> On 2022-10-09 12:59:09 -0400, Thomas Passin wrote:
>>
https://stackoverflow.com/questions/4284313/how-can-i-check-the-syntax-of-python-script-without-executing-it
>>
>> People seemed especially enthusiastic about the one-liner from jmd_dk.
>
> I d
hen make a new file commencing with the
next unindented line after the error, with all preceeding lines
commented out (to keep the line numbers the same). Then run the check
again. Repeat until the file's empty or there are no errors.
This doesn't sound very complex.
Cheers,
Camer
On Mon, 10 Oct 2022 at 06:50, Antoon Pardon wrote:
> I just want a parser that doesn't give up on encoutering the first syntax
> error. Maybe do some semantic checking like checking the number of parameters.
That doesn't make sense though. It's one thing to keep going after
finding a non-syntacti
Am Sun, Oct 09, 2022 at 07:51:12PM +0200 schrieb Antoon Pardon:
> >But the point is: you can't (there is no way to) be sure the
> >9+ errors really are errors.
> >
> >Unless you further constrict what sorts of errors you are
> >looking for and what margin of err
> On 9 Oct 2022, at 18:54, Antoon Pardon wrote:
>
>
>
> Op 9/10/2022 om 19:23 schreef Karsten Hilbert:
>> Am Sun, Oct 09, 2022 at 06:59:36PM +0200 schrieb Antoon Pardon:
>>
>>> Op 9/10/2022 om 17:49 schreef Avi Gross:
>>>> My guess is that fi
Op 9/10/2022 om 21:44 schreef Avi Gross:
But an error like setting the size of a fixed length data structure to the
right size may result in oodles of errors about being out of range that
magically get fixed by one change. Sometimes too much info just gives you a
headache.
So? The user of
fects anyway).
One issue is could be that compilers which generate executables are
generally thorough and slow, while the compilers which generate
byte-code for immediate consumption by an interpreter are generally
simple and fast. So there is more incentive for the former to discover
as many errors as
faster later.
I just want a parser that doesn't give up on encoutering the first syntax
error. Maybe do some semantic checking like checking the number of parameters.
I will say that often enough a program could report more possible errors.
Putting your code into multiple files and module
faster later.
I just want a parser that doesn't give up on encoutering the first syntax
error. Maybe do some semantic checking like checking the number of parameters.
I will say that often enough a program could report more possible errors.
Putting your code into multiple files and module
I will say that those of us meaning me, who express reservations are not
arguing it is a bad idea to get more info in one sweep. Many errors come in
bunches.
If I keep calling some function with the wrong number or type of arguments,
it may be the same in a dozen places in my code. The first
of code that are not really be evaluated
till later. Some code is built on the fly. And some errors are not errors
at first. Many languages let you not declare a variable before using it or
allow it to change types. In some, the text is lazily evaluated as late as
possible.
I will say that often
On 2022-10-09 18:51, Antoon Pardon wrote:
Op 9/10/2022 om 19:23 schreef Karsten Hilbert:
Am Sun, Oct 09, 2022 at 06:59:36PM +0200 schrieb Antoon Pardon:
Op 9/10/2022 om 17:49 schreef Avi Gross:
My guess is that finding 100 errors might turn out to be misleading. If you
fix just the first
PyCharm.
Does a good job of separating these are really errors from do you really mean
that warnings from this word is spelled right.
https://www.jetbrains.com/pycharm/
From: Python-list on
behalf of Antoon Pardon
Date: Sunday, October 9, 2022 at 6:11 AM
To: python-list@python.org
Subject
Op 9/10/2022 om 19:23 schreef Karsten Hilbert:
Am Sun, Oct 09, 2022 at 06:59:36PM +0200 schrieb Antoon Pardon:
Op 9/10/2022 om 17:49 schreef Avi Gross:
My guess is that finding 100 errors might turn out to be misleading. If you
fix just the first, many others would go away.
At this moment
On 2022-10-09 19:23:41 +0200, Karsten Hilbert wrote:
> Am Sun, Oct 09, 2022 at 06:59:36PM +0200 schrieb Antoon Pardon:
> > Op 9/10/2022 om 17:49 schreef Avi Gross:
> > >My guess is that finding 100 errors might turn out to be misleading. If you
> > >fix just the first
On 2022-10-09 12:59:09 -0400, Thomas Passin wrote:
> https://stackoverflow.com/questions/4284313/how-can-i-check-the-syntax-of-python-script-without-executing-it
>
> People seemed especially enthusiastic about the one-liner from jmd_dk.
I don't think that one-liner solves Antoon's requirement of
Am Sun, Oct 09, 2022 at 06:59:36PM +0200 schrieb Antoon Pardon:
> Op 9/10/2022 om 17:49 schreef Avi Gross:
> >My guess is that finding 100 errors might turn out to be misleading. If you
> >fix just the first, many others would go away.
>
> At this moment I would prefer a t
tool that tries to find as many syntax errors as possible in
a python file. I know there is the risk of false positives when a tool tries
to recover from a syntax error and proceeds but I would prefer that over the
current python strategy of quiting after the first syntax error. I just want
a tool
Op 9/10/2022 om 17:49 schreef Avi Gross:
My guess is that finding 100 errors might turn out to be misleading. If you
fix just the first, many others would go away.
At this moment I would prefer a tool that reported 100 errors, which would
allow me to easily correct 10 real errors, over the
On 2022-10-09 12:09:17 +0200, Antoon Pardon wrote:
> I would like a tool that tries to find as many syntax errors as possible in
> a python file. I know there is the risk of false positives when a tool tries
> to recover from a syntax error and proceeds but I would prefer that over the
resume checking the
next function. But what if a function defines local functions within it?
What if the mistake in one line of code could still allow checking the next
line rather than skipping it all?
My guess is that finding 100 errors might turn out to be misleading. If you
fix just the first
I would like a tool that tries to find as many syntax errors as possible
in a python file. I know there is the risk of false positives when a
tool tries to recover from a syntax error and proceeds but I would
prefer that over the current python strategy of quiting after the first
syntax error
On 11/14/21, Marco Sulla wrote:
> On Sun, 14 Nov 2021 at 16:42, Barry Scott wrote:
>
>> On macOS .dynlib and Unix .so its being extern that does this.
>
> And extern is the default. I understand now.
Per Include/exports.h and Include/pyport.h, Python should be built in
Unix with "default" visibi
On Sun, 14 Nov 2021 at 16:42, Barry Scott wrote:
>
> Sorry iPad sent the message before it was complete...
>
> > On 14 Nov 2021, at 10:38, Marco Sulla wrote:
> >
> > Okay, now the problem seems to be another: I get the same "unresolved
> > external link&qu
Sorry iPad sent the message before it was complete...
> On 14 Nov 2021, at 10:38, Marco Sulla wrote:
>
> Okay, now the problem seems to be another: I get the same "unresolved
> external link" errors, but only for internal functions.
>
> This seems quite normal. The
Okay, now the problem seems to be another: I get the same "unresolved
external link" errors, but only for internal functions.
This seems quite normal. The public .lib does not expose the internals
of Python.
The strange fact is: why can I compile it on Linux and MacOS? Their
external
arco Sulla wrote:
> >>
> >> It seems that on Windows it doesn't find python3.lib,
> >> even if I put it in the path. So I get the `unresolved external link`
> >> errors.
> >
> > I think you need the python310.lib (not sure of file name) to get
1 - 100 of 984 matches
Mail list logo
